Replies: 2 comments
-
I usually do not tag, and instead require the package as If you do rather tag then I think I'd make it 1.2.99 or something like that, or you can use |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you! The second link is what I was looking for and did not find. And the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've forked a package and fixed a bug in it. Now I want to tag it, so that I can use the version in my project's
composer.json
file.Let's assume the latest upstream version is v1.2.3. Shall I create a tag v1.2.4 in my own repository? This will lead to confusion when upstream releases that version, regardless if my patch has been merged or not. (because nobody can say if it's safe remove the repository from composer.json)
How can I name my tags so that it is clear that the tag is local to my forked repository?
The official docs are not very clear on that, at least suffixes "alpha", "beta" and "rc" are allowed.
When trying tag names like "v1.2.4-myfork-1" composer tells me:
Beta Was this translation helpful? Give feedback.
All reactions