-
Notifications
You must be signed in to change notification settings - Fork 270
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
Master commits break projects using the latest version #709
Comments
Thanks Mario. I’m not sure I understand the concern though. Are you using
the source code directly or public repos like npm and DockerHub where the
branch doesn’t matter? If you are linked to the source directly, mind
sharing a bit about your workflow?
-Brandon
On Tue, Oct 18, 2022 at 3:09 AM Mario Arranz ***@***.***> wrote:
Hi, @bbyars <https://github.com/bbyars> thanks for this project, super
useful library for bdd tests and reproducing different scenarios.
We've recently had an issue due to a change in the entrypoint
<06a477c>
in the master branch so I thought I would open a ticket to ask for branch
commits instead of committing to master directly.
I know we should have pointed to a version tag instead of to latest but I
think it's a good practise that is worth mentioning.
Thanks again for all the effort maintaining the library!
—
Reply to this email directly, view it on GitHub
<#709>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARFP6K7LRD26EVHQIU2QLWDZZNLANCNFSM6AAAAAARH5HHCM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Sent from Gmail Mobile
|
When using docker and referring to the library as |
There are certainly those who argue the opposite, that trunk based development is the better way to go. |
Hi, @bbyars thanks for this project, super useful library for bdd tests and reproducing different scenarios.
We've recently had an issue due to a change in the entrypoint in the master branch so I thought I would open a ticket to ask for branch commits instead of committing to master directly.
I know we should have pointed to a version tag instead of to latest but I think it's a good practise that is worth mentioning.
Thanks again for all the effort maintaining the library!
The text was updated successfully, but these errors were encountered: