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 Jan 11, 2024. It is now read-only.
What this means is that my mq changesets are put in the "secret" phase instead of "draft" (the default). The thing with "secret" changesets is that they are not pushed to remote servers. This is a feature, not a bug. This is to prevent you from accidentally publishing changesets you don't intend to.
For try pushes, we want to push secret changesets. But, we don't want to mark them as published.
I think the solution here is to record the phase of outgoing changesets before push then reset them after push.
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.
I have the following in my hgrc:
What this means is that my mq changesets are put in the "secret" phase instead of "draft" (the default). The thing with "secret" changesets is that they are not pushed to remote servers. This is a feature, not a bug. This is to prevent you from accidentally publishing changesets you don't intend to.
For try pushes, we want to push secret changesets. But, we don't want to mark them as published.
I think the solution here is to record the phase of outgoing changesets before push then reset them after push.
The text was updated successfully, but these errors were encountered: