-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
delete master branch, potentially turn into a tag? #386
Labels
bug
Something isn't working
Comments
Hello @karlbrown-va. Thank you for your report. The master branch links to v1 tag. The latest major tag points to the main branch. We recommend to use tags, because the latest code of the branches can be carrying breaking changes. |
Hi, understood. However you might consider deleting the master branch. It’s
a bit confusing to have both master and main as branches. One would assume
master would point to the tip. We’ve changed our code to use tags, but the
behavior of master being v1 is unexpected and at the very least maybe
consider documenting this if it’s not already and if you want to keep the
master branch as a branch.
On Dec 23, 2021, at 09:24, Dmitry Shibanov ***@***.***> wrote:
Hello @karlbrown-va <https://github.com/karlbrown-va>. Thank you for your
report. The master branch links to v1 tag. The latest major tag points to
the main branch. We recommend to use tags, because the latest code of the
branches can be carrying breaking changes.
—
Reply to this email directly, view it on GitHub
<#386 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANONOZITBYT6JLLBK2WGQ6TUSMWLBANCNFSM5KSZKCGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
deining
pushed a commit
to deining/setup-node
that referenced
this issue
Nov 9, 2023
* chore: add additional log notes * feat: add `fetch` input Ref actions#386 * fix: add warnings about not fetching * docs: `fetch` input & large repos FAQ * chore: fix typo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
At this point #171 the
master
branch was changed tomain
. However, we still had actions pointing tomaster
, which one would normally assume would link to the latest tip. Sincemaster
is now moribund this branch should be deleted, which will likely cause existing actions to break. Or, the branch can be deleted and a new tag can be maintained of 'master' until such time as people have migrated over to usingmain
orv2
etc.Action version:
v2.5
Platform:
Runner type:
Tools version:
n/a
Repro steps:
create an action linking to setup-node/master. Notice how it pulls in an older version.
Expected behavior:
Master should link to the tip.
Actual behavior:
Master is now a stale branch. So the branch should be deleted or replaced with a continuously updating tag.
The text was updated successfully, but these errors were encountered: