You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- 1Comments are not for extended discussion; this conversation has been moved to chat.maple_shaft– maple_shaft ♦2017-06-27 11:35:33 +00:00Commented Jun 27, 2017 at 11:35
- 4The simple binary logic of fire vs keep may work for computers, it doesn't for people. You may want to check out workplace.stackexchange.com for your question once you feel ready to address it beyond the Git aspect.Frank– Frank2017-06-27 13:47:50 +00:00Commented Jun 27, 2017 at 13:47
- Point out that Git looks good on the CV ;-)Mawg– Mawg2017-06-28 10:25:05 +00:00Commented Jun 28, 2017 at 10:25
- 1This is really a people / psychology problem, not a software engineering problem.Jesper– Jesper2017-06-29 13:32:58 +00:00Commented Jun 29, 2017 at 13:32
- @Jesper yes and no. I was going to put it on workplace but saw potential for some very Git specific advice (which I received!) that might be immediately applicable.Gusdor– Gusdor2017-06-29 13:52:06 +00:00Commented Jun 29, 2017 at 13:52
| Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you