Feature request: Add the ability to create PRs from a tag to a branch (production < v1.1.1) #23870
-
Hello, I kind of use PRs to validate deploys to environments: So after i create a new release, via github releases, i get a tag, lets say v1.1.1. If i want to deploy v1.1.1 to the production environment, i open a PR from a branch that is at v1.1.1 to the production branch. The team than decides if it approves the PR and when merging the CI/CD kicks in when a new commit is pushed to production. It would be cool if i could open the PRs directly from the tag v1.1.1 to the production branch, instead of having a branch pointing to v1.1.1 just for the PR. Something like production < v1.1.1 : https://github.com/NMFR/my-repo/compare/production…v1.1.1?expand=1 Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 25 comments 3 replies
-
Hi @nmfr, Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration. Cheers! |
Beta Was this translation helpful? Give feedback.
-
Whilw your feature request makes perfect sense in your case, I think it is not as intuitive in general: pull requests are not static pointers to a commit, but you can push new commits to a PR, force-push entirely new contents to it and do all things that in the world of git are meant for branches and not tags. What is your normal branching model for your major/minor/feature releases? Maybe there’s a middle ground to be found that works. |
Beta Was this translation helpful? Give feedback.
-
I’ve also just stumbled upon this issue, exactly the same workflow: I can create PR’s from master to pre-release where I can edit changes and finally issue a command to create a version bump, tag and merge to the pre-release. This is a beta branch which receives updates often. Once a month I want to merge a specific version from the developer branch into the release branch. This should not be the HEAD of pre-release since there might be changes on it which have not been tested thoroughly enough. It would be awesome if I could create a PR from a specific version tag (which are on the pre-release) to release and merge if everything checks out. In this case, it doesn’t make sense to allow changes to the PR. The version should be immutable so if I want to change what is merged to public release I would close such a PR and create a new one with HEAD from another version tag.
|
Beta Was this translation helpful? Give feedback.
-
Another use case for this is when I fork a repo, and I want to make a PR against a previous release for which there is no branch in the original repo, only a tag. And since I don’t control the original repo, I can’t make a branch. |
Beta Was this translation helpful? Give feedback.
-
Facing the same use case as OP. |
Beta Was this translation helpful? Give feedback.
-
Yes, I also need this feature from github. |
Beta Was this translation helpful? Give feedback.
-
I too have an use case for this and upvoted as well!
I've not created production branch previously pointing to particular tag (only tracked via tag) and I want to create new branch and open PR from that tag to my new branch |
Beta Was this translation helpful? Give feedback.
-
Another important issue to resolve here is doing PRs for GitHub Actions. Versioning of the latter is done via tags, and without ability to change tags in PRs, PRs on Actions afer merging need manual adjustment of tags in master. |
Beta Was this translation helpful? Give feedback.
-
This feature would be great, along with some tag protection rules |
Beta Was this translation helpful? Give feedback.
-
I'd be keen to see this feature too. |
Beta Was this translation helpful? Give feedback.
-
Today I faced this same situation. It would be great if Github had this feature. |
Beta Was this translation helpful? Give feedback.
-
waiting for this feature |
Beta Was this translation helpful? Give feedback.
-
This feature is needed!! |
Beta Was this translation helpful? Give feedback.
-
I'll upvote this one, too. I just ran into a case where I need this, and although you can select a tag while creating a PR, the actual creation of it is blocked once you do. |
Beta Was this translation helpful? Give feedback.
-
I think this feature is most necessary and urgent. I recently created a pull request to a parent project, and then continued development in my own repository preparing for the next major release; all my pushes got appended to the pull request, polluting it and rendering it useless. |
Beta Was this translation helpful? Give feedback.
-
I need this feature too for the reasons above. |
Beta Was this translation helpful? Give feedback.
-
i would like this feature too. |
Beta Was this translation helpful? Give feedback.
Hi @nmfr,
Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.
Cheers!