Skip to content
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

Publish (also) as a branch #5

Open
Treora opened this issue Mar 17, 2020 · 2 comments · May be fixed by #9
Open

Publish (also) as a branch #5

Treora opened this issue Mar 17, 2020 · 2 comments · May be fixed by #9

Comments

@Treora
Copy link

Treora commented Mar 17, 2020

It would be great to be able to make all tags form a branch, e.g. release.

Besides making it easier to overview the tags, it would let a client run npm install https://git.example.com/project#release to get the latest version.

Projects may even want this branch to be called master (and have the source in e.g. develop) so that npm install https://git.example.com/project would install the latest release, according to the npm docs:

If neither #<commit-ish> or #semver:<semver> is specified, then master is used.

@Rush
Copy link
Owner

Rush commented Apr 18, 2020

Can you propose example syntax? And maybe even submit a PR for it? :-)

@Treora Treora linked a pull request Apr 23, 2020 that will close this issue
@Treora
Copy link
Author

Treora commented Apr 23, 2020

Can you propose example syntax?

I guess just --branch <branchname> would be adequate?

And maybe even submit a PR for it? :-)

#9! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants