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.
-
What heuristics do you suggest for deciding which commits to squash, and which to keep separate?outis– outis2021-02-11 04:21:11 +00:00Commented Feb 11, 2021 at 4:21
-
Here's an example from Linux: Linus Torvalds considers the commit history the same as code. So, in exactly the same way that you refactor code so that the code looks like you knew exactly what you wanted to build and how from day 1, you refactor the history so that it looks like you knew exactly what steps to take to get to the result. Of course, this is an extreme example, because Linux has 3000 developers and there is a commit every couple of seconds (and the rate of commits seems to be increasing super-linearly), so a clean history is vital.Jörg W Mittag– Jörg W Mittag2021-02-11 08:45:02 +00:00Commented Feb 11, 2021 at 8:45
-
For my current project, I'm pushing new code to the server almost every week with new features. Let's say in a particular week I add 3 new features. Would you consider this to be a "release" to then be tagged?Eric– Eric2021-02-11 14:12:52 +00:00Commented Feb 11, 2021 at 14:12
-
1I'd recommend squashing the commits for each feature, so you should have only 3 commits for the 3 features. I say this because most of the time commits in one feature consist of multiple small commits. There is no defined size of a release. You (organization) define it. A release is defined by a cadence or a need - say a weekly, monthly or quarterly release. An example of a need is a security patch or could be based on an agreement in a contract. So if you've added 3 new features and its time to release based on your cadence or need, then by all means - tag and release.m_vemuri– m_vemuri2021-02-12 01:41:58 +00:00Commented Feb 12, 2021 at 1:41
Add a comment
|
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