Repository navigation
onboard-openneuro: nemar auth login --yes - #107
Merged
Merged
Conversation
neuromechanist
force-pushed
the
ci/login-yes
branch
from
September 8, 2026 16:48
e287f3a to
86120c8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nemar-cli v0.10.0 (nemarOrg/nemar-cli#1307) replaces password sign-in with browser sign-in and keeps
nemar auth login --keyas the paste path this workflow uses in all three jobs. Verified against the dev worker with the new code: a fresh config, stdin closed, and a service-kind owner key (whatNEMAR_ADMIN_API_KEYbecomes after migration 0082) log in with "Welcome back" and run admin commands, so no change is required for the release.This adds
--yesto the three login lines as a precaution: the paste path asks "Add a different account?" only when the config already holds an active account, which a GitHub-hosted runner never has, but a cached config must not be able to hang a job on a prompt.