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
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
This workspace is based on this NCS-historical-health branch. When I pushed results using osrelease, it pushed them to a release-candidates branch that was based on master, meaning that the subsequent PR to merge with the NCS-historical-health branch had a load of unwanted code changes.
I think there are two issue: osrelease bases release-candidates branch of the default branch if it doesn't exist. But also, it reuses it if it does. Which is fine, as long as the user has deleted old versions of that branch once results have been merged. But if not, it can cause all kinds of issues (e.g. old release-candidates branch being based on master when you're working on a branch
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This workspace is based on this
NCS-historical-health
branch. When I pushed results usingosrelease
, it pushed them to arelease-candidates
branch that was based onmaster
, meaning that the subsequent PR to merge with theNCS-historical-health
branch had a load of unwanted code changes.From @bloodearnest:
The text was updated successfully, but these errors were encountered: