"Ignore file" uses confusing verbiage

Please describe the problem you think should be solved

When right-clicking a changed file, a context menu shows up with several options, two of which are “Ignore file” and “Ignore all files”. It’s not readily apparent what’s actually going to happen when you click either of those. Is it going to just ignore them in Desktop? Does it add the files to your .gitignore? It’s only apparent that it’s the latter after you’ve clicked them.

[Optional] Do you have any potential solutions in mind?

We discussed this internally and threw out a few options that attempt to more explicitly describe what’s happening for both beginners and more advanced Git users.

1. “Ignore file with .gitignore” / “Ignore all .gradle files with .gitignore”
2. “Ignore file (add to .gitignore)” / “Ignore all .gradle files (add to .gitignore)”
3. “Ignore file in Git” / “Ignore all .gradle files in Git”

I think all of them are improvements over what we have today, but I’m curious if there are any other thoughts or considerations. The length of the “Ignore all…” for (1) and (2) above doesn’t feel great, but maybe ok?

When we settle on something, this feels like something that could be a good-first-issue.

[PaulViola]

I’m happy to help! Here are the screenshots.

“Ignore file with .gitignore” / “Ignore all .gradle files with .gitignore”

---

“Ignore file (add to .gitignore)” / “Ignore all .gradle files (add to .gitignore)”

---

“Ignore file in Git” / “Ignore all .gradle files in Git”

[billygriffin]

@PaulViola As long as you’re ok with folks potentially pushing back in the PR, feel free to go forth with option 2 since it seems like folks generally think that’s a good idea. It doesn’t strike me as wildly long to where it’s problematic visually. Thanks for showing us the options!

One thing for the PR - please ensure the capitalization is correct based on whether it’s macOS (labeled as Darwin in the code base) or not (macOS is title case and otherwise it’s sentence case).