Replies: 1 comment
-
|
I have the same issue. Here is another thread discussing this as well, I believe: https://github.com/orgs/community/discussions/17292 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
I'm using Actions with environments set to auto-create deployments. This is populating the deployment history for our repo.
We're using a git-flow process, where our
mainbranch represents our shipped code and ourdevelopbranch is the default branch used for development.When deploying, we merge code from
developtomain, then trigger a deployment frommain.The GitHub UI seems to be looking at the last commit on
main, seeing that it's a PR fromdevelop, and showingdevelopas the source branch in the deployment history, even though the commit it references (the merge of thedevelop->mainPR) isn't present ondevelop.The underlying deployment record via the API correctly attributes the source of the deployment to
main, but the UI showsdevelopinstead.Is there any way to avoid this?
Beta Was this translation helpful? Give feedback.
All reactions