[Build & Deploy] Deploy PRs (develop to master) seem to be broken
See original GitHub issueDescription
When you open a PR from develop
to master
it does not deploy (at least several have not in the last couple weeks.
Following the doc, it seems that a production deploy should happen. Currently, we do not have access to opensource in Amplify to check the logs / see what’s happening when these PRs are opened.
Acceptance Criteria
- Figure out why deployments from develop > master aren’t working
- provide a
fix
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How I learned to stop worrying and push to master
Having develop and main seems like more of a pain than PRs to main and using release branches. This model is also very...
Read more >GitHub action PR to deploy to master continuing even though ...
It seems that the auto-pr to master from develop has been failing for quite some time, but deploying anyway. All of the deploy...
Read more >Pull requests not triggering build - CircleCI Discuss
It correctly triggers build on commits to master and ignores commits on other branches. However any pull request from another branch into master...
Read more >Build Origin PRs (merge with base branch) conducts rebuilds ...
When 'Build Origin PRs (merge with base branch)' is selected any PR's which are filed against a base branch are re-triggered when the...
Read more >Git branch policies and settings - Azure Repos - Microsoft Learn
Branch policies help teams protect their important branches of development. Policies enforce your team's code quality and change management ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the issue here refers to one caused by the branch protection in this repository, it has currently been mitigated by removing the protection rule. This can be fixed by changing the workflows to handle branch protection and reenabling the protections.
fixed when the team team removed branched protection rules that were causing this error.