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
I am using semantic release for handling versioning in my repo. But recently am facing issues when running the job in gitlab ci. I have a beta branch where beta versions are released. But when the changes are added to beta semantic release runs and shows
The local branch beta is behind the remote one, therefore a new version won't be published
Using the debug flag got some more logs
error: failed to push some refs to 'https://username:[secure]@repo_url'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and integrate the remote changes
hint: (e.g. 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards'in'git push --help'for details.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using semantic release for handling versioning in my repo. But recently am facing issues when running the job in
gitlab ci
. I have a beta branch where beta versions are released. But when the changes are added to beta semantic release runs and showsUsing the
debug
flag got some more logsBeta Was this translation helpful? Give feedback.
All reactions