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

History for Commit message #2002

Closed
hajo4 opened this issue Nov 21, 2013 · 5 comments
Closed

History for Commit message #2002

hajo4 opened this issue Nov 21, 2013 · 5 comments

Comments

@hajo4
Copy link

hajo4 commented Nov 21, 2013

Just like here, for entering the title of new issues.

That would make it more easy to re-use
one of the previous commit messages,
if you revisited+fixed an earlier edit,
after some other saves.

@tmcw
Copy link
Contributor

tmcw commented Nov 21, 2013

This doesn't seem like something that should be in the domain of iD; a user can easily pull up their own commit history.

@jfirebaugh
Copy link
Member

I could see this being done in a helpful yet unobtrusive way. iD could do a changeset API request behind the scenes and then autocomplete commit messages based on that.

@hajo4
Copy link
Author

hajo4 commented Nov 23, 2013

When mapping, I often have cycles like

  • "paint new houses",
  • "new pub x"
  • "added housenumbers"
  • "new shop y"
  • "more new houses"
  • "update data for x"
    etc.

So, re-using old commit-messages would be really helpful.

@tmcw : "easily" as in

  • open new tab
  • go to user-page at www.openstreetmap.org/user/xxx
  • go to "My Edits"
  • find old commit-message
  • copy
  • change back to map-tab
  • paste into field for commit-comment

as opposed to "cllck+edit" ?

Also, no need to go for old commit-messages in the database,
just remember the commits from the current session.

@tmcw
Copy link
Contributor

tmcw commented Nov 23, 2013

If the commit message uses a input type=text instead of a textarea, then we could just use browser autocomplete.

@HolgerJeromin
Copy link
Contributor

IMO no need for calling the API. This is better stored in the browser storage.

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

No branches or pull requests

4 participants