Automated release should not need to push up to develop #710
Assignees
Comments
GCHQ-Developer-530
added a commit
that referenced
this issue
May 23, 2023
Add git stash to automated release step so that it can successfully create a develop -> main PR . #710
GCHQ-Developer-530
added a commit
that referenced
this issue
May 23, 2023
…essage Add git stash to automated release step and remove commit message so that it can successfully create a develop -> main PR . #710
3 tasks
GCHQ-Developer-530
added a commit
that referenced
this issue
May 23, 2023
…essage Add git stash to automated release step and remove commit message so that it can successfully create a develop -> main PR . #710
GCHQ-Developer-741
pushed a commit
that referenced
this issue
Jun 2, 2023
…essage Add git stash to automated release step and remove commit message so that it can successfully create a develop -> main PR . #710
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary of the bug
Currently the github workflow ic-ui-kit-release fails as it cannot push the release check changes onto the develop branch since it's protected.
🪜 How to reproduce
Tell us the steps to reproduce the problem:
🧐 Expected behaviour
Should create develop -> main PR.
📸 Screenshots or code
Additional info
Potentially as easy as adding git stash after line 20 of the workflow file.
The text was updated successfully, but these errors were encountered: