Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jj should walk users through setting their email/name #530

Closed
jsoref opened this issue Sep 9, 2022 · 0 comments · Fixed by #624
Closed

jj should walk users through setting their email/name #530

jsoref opened this issue Sep 9, 2022 · 0 comments · Fixed by #624

Comments

@jsoref
Copy link
Collaborator

jsoref commented Sep 9, 2022

Description

Right now searching for jj "no email configured" yields:

It looks like there aren't many great matches for your search

Google is right

Steps to Reproduce the Problem

  1. install jj
  2. clone a repo
  3. use jj log

Expected Behavior

At some point in this process (possibly at clone, possibly at log), the user should be directed to how to set up their name/email

Actual Behavior

(no email configured) as noted in #528

Specifications

  • Platform:
  • Version: 0.4.0
martinvonz added a commit that referenced this issue Oct 10, 2022
This commit adds a reminder in `finish_transaction()` if the user
hasn't configured their name and email. That means they'll get a
reminder after most mutating commits, except for commands that only
snapshot the working copy, and a few more cases.

Closes #530.
martinvonz added a commit that referenced this issue Oct 10, 2022
This commit adds a reminder in `finish_transaction()` if the user
hasn't configured their name and email. That means they'll get a
reminder after most mutating commits, except for commands that only
snapshot the working copy, and a few more cases.

Closes #530.
martinvonz added a commit that referenced this issue Oct 10, 2022
This commit adds a reminder in `finish_transaction()` if the user
hasn't configured their name and email. That means they'll get a
reminder after most mutating commits, except for commands that only
snapshot the working copy, and a few more cases.

Closes #530.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant