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

Generic branch aliases (beyond the built-in "latest") #893

Closed
itamarst opened this issue Aug 18, 2014 · 2 comments
Closed

Generic branch aliases (beyond the built-in "latest") #893

itamarst opened this issue Aug 18, 2014 · 2 comments
Labels
Improvement Minor improvement to code Needed: patch A pull request is required

Comments

@itamarst
Copy link

We have a release tag and a release branch, and we'd like to continue pushing documentation improvements to the release branch so documentation gets updated without having to do a release.
Given RTD's use of branch names in the URL/version listing, however, we need to name the release branch in a way that looks OK as part of a URL, which is a bit silly.

It would be nice if branches could be configured with aliases, so we could say something like "branch release/myproject-0.1 should display as 0.1".

@ericholscher
Copy link
Member

👍 on adding an alias concept. The names of VCS tags & branches aren't always meant to be user facing. We should add the ability to add a specific alias to each Version, which would then be it's user facing slug.

@ericholscher ericholscher added Needed: patch A pull request is required and removed Needed: design decision A core team decision is required labels Sep 18, 2015
@agjohnson
Copy link
Contributor

Moving this to #4001, where we discuss adding more version aliasing rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code Needed: patch A pull request is required
Projects
None yet
Development

No branches or pull requests

4 participants