-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revise adr to support fetch-refs #155
Conversation
51176b6
to
8c9b201
Compare
@@ -43,12 +43,18 @@ We want to take this opportunity to make behavioral changes, from v1. This docum | |||
fetch-depth: | |||
description: 'Number of commits to fetch. 0 indicates all history.' | |||
default: 1 | |||
fetch-refs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opted to update existing ADR rather than create a new document. This single file gives a holistic picture.
Would be great to see this merged in. Any update on this? |
Any update on this? |
It is really bad this PR is hanging for so long This is a must have for all people using |
@ericsciple any updates on this? |
Did this ever get anywhere? @chrispat |
@ericsciple @chrispat bump. It would be really nice to have this! |
I am going to close this as there are no plans to add this feature at this time. |
Propose adding a new input
fetch-refs
to specify additional refs to fetch.Customers commonly want to fetch additional branches or tags. This has come up in issues and the docs have improved to provide guidance (add additional
run
step).Given how common these scenarios are, we should provide a first-class input.
Another common scenario is to compare code coverage numbers between the PR merge commit, and the PR base branch.