Feature request: Add the ability to create PRs from a tag to a branch (production < v1.1.1)

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.1https://github.com/NMFR/my-repo/compare/production…v1.1.1?expand=1

Thanks in advance.

1 Like

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!

1 Like

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.

1 Like

I’ve also just stumbled upon this issue, exactly the same workflow:
I have a master branch, a pre-release branch and a release branch.

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.

The automation for these is done using GitHub Actions which is the reason I chose PR’s as a release tool