You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we deploy the extension, there's a job that that bumps the versions to the appropriate version before deploying to the stores. After deployment succeeds, the pipeline would automatically open a PR that would request to merge these version changes back to the repo. It was helpful to make sure our versions stay up to date in the repo.
Right now, it's opening a blank PR to the repo after deployment, which gets automatically closed by GitHub. Let's make sure this job correctly opens the PR to merge these version changes back to the repo.
BONUS POINT
In the past, when this PR was working, the tests would not automatically run when the PR was programmatically opened. Because of this, we'd be unable to merge this PR unless we nudged the CI by committing an empty commit to this branch. Is it possible to solve this issue while we're fixing this?
The text was updated successfully, but these errors were encountered:
When we deploy the extension, there's a job that that bumps the versions to the appropriate version before deploying to the stores. After deployment succeeds, the pipeline would automatically open a PR that would request to merge these version changes back to the repo. It was helpful to make sure our versions stay up to date in the repo.
Right now, it's opening a blank PR to the repo after deployment, which gets automatically closed by GitHub. Let's make sure this job correctly opens the PR to merge these version changes back to the repo.
BONUS POINT
In the past, when this PR was working, the tests would not automatically run when the PR was programmatically opened. Because of this, we'd be unable to merge this PR unless we nudged the CI by committing an empty commit to this branch. Is it possible to solve this issue while we're fixing this?
The text was updated successfully, but these errors were encountered: