Hot answers tagged

74 votes
Accepted

When should a commit not be version tagged?

SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to ...
Alex Reinking's user avatar
20 votes
Accepted

Is it bad practice to create a git tag for every successful continous deployed build?

In practice, because every commit in a git system already has a hash, if all you need is a unique identifier to reproduce a build, or identify a particular state of your branch, you already have that ...
FrobberOfBits's user avatar
12 votes

When should a commit not be version tagged?

Version numbers are allocated to releases. In general not every commit should be a release. There are several reasons for this. Firstly while you say you "test" every commit there are levels of ...
Peter Green's user avatar
  • 2,242
7 votes

Isn't there a substantial problem with SVN tags?

Subversion's sparse directories is what you are looking for. First time checkout, you should run: svn checkout --depth immediates <URL> This will only checkout the first level, thus only ...
Hans Deragon's user avatar
5 votes

How to properly manage bugfixes for released versions in git flow

You are on the right track. Hotfixes to production should be branched from the master branch. I know you're not calling it a hotfix, but it functionally is, as it will go before any new feature ...
Flater's user avatar
  • 48.7k
5 votes

Divergent Bodies of Truth, Relationships of Concepts

What you're describing is the task of cluster analysis. The goal is to find distinct clusters in data where the elements in the cluster are correlated. The attributes of the data form the "context" ...
Samuel's user avatar
  • 9,187
4 votes

git tagging comments - best practices

A tag should be created for significant commits — something meaningful. This is a bit open-ended, but most times a tag corresponds to a release, and this is why you tend to see tags like v1.3.5....
Greg Burghardt's user avatar
4 votes
Accepted

What is the better search system, user defined tags or pre defined attribute fields?

I'm in favor of a tagging system over predefined fields when many of them are just going to be N/A. All predefined fields do in those cases is suggest things to think about adding. I don't need a pile ...
candied_orange's user avatar
4 votes

Is manually tagging content an ideal start for eventual machine learning?

You're building a training set. This is used to teach the AI what you want. The important thing is to be careful that the set doesn't contain false tells like a red and white checkered table cloth ...
candied_orange's user avatar
4 votes

Using tags instead of different branches

It's best not to use git flow for a project where you aspire to continuous delivery. As Vincent Driessen, the originator of Git Flow writes: If your team is doing continuous delivery of software, I ...
bdsl's user avatar
  • 2,725
4 votes

How to properly manage bugfixes for released versions in git flow

You can deal with them almost like hotfixes (or simply call a hotfix branch "bugfix branch"). Distinguishing between hotfixes and "less critical fixes" does not make a huge ...
Doc Brown's user avatar
  • 206k
3 votes

How to properly manage bugfixes for released versions in git flow

Normally you would have every released branch tagged in git. So you look for the tag, and start branching from that. So if you want 2.0.8 with fixes, you branch from 2.0.8. Eventually you are done and ...
gnasher729's user avatar
  • 44.7k
3 votes
Accepted

using git, bringing old tagged releases up to date

In my previous company we had the same problem, we had to "update" old releases e.g. to allow them to run on modern OS oe support a new version of the old hardware. Our solution was your #1, ...
Davide's user avatar
  • 46
3 votes

When should a commit not be version tagged?

Seems to obvious to say, but: a version numbers purpose is to let you easily determine what version of the software anyone is running. If there is any chance of anyone having access to a particular ...
ANone's user avatar
  • 311
3 votes
Accepted

Divergent Bodies of Truth, Relationships of Concepts

This is a fairly broad question. It's not clear to me if you're looking for algorithms that find the potential tags, or algorithms that can deal witht the fact that the universe is not black or ...
Christophe's user avatar
  • 76.8k
3 votes
Accepted

Best GIT approach to educational project

As a cautionary note up-front, the way that git works means that if the solution is stored in the same repository as the project definition and if students are expected to clone that repository to get ...
Bart van Ingen Schenau's user avatar
2 votes

using git, bringing old tagged releases up to date

A tag denotes a specific point in development history. It should not change, at all. Ideally, build should be reproducible. This means checking out a tag and building it should - bit-for-bit - produce ...
Polygnome's user avatar
  • 2,046
2 votes

How to properly manage bugfixes for released versions in git flow

Ideally, management should have thought about this when ordering the work for the development team and scheduling the release. I'm not surprised that the standard GitFlow model doesn't account for ...
Thomas Owens's user avatar
  • 82.4k
1 vote
Accepted

Should tags be introduced on commits still in Pull Request branches outside of main/master branch?

Tags are used to identify specific commits on long-lived branches for specific reasons. This is so you can quickly check out the codebase at that specific commit. As in your case, tagging with a ...
mmathis's user avatar
  • 5,458
1 vote

How to properly manage bugfixes for released versions in git flow

I agree with the other answers that the default solution for you would be to create a hotfix branch off of master, and put the bug fixes there. However, since you mentioned some of the bug fixes may ...
TTT's user avatar
  • 246
1 vote

using git, bringing old tagged releases up to date

I'd suggest making a separate versioned maintenance branch, and create a new versioned tag whenever you re-release an old version with new build environment. That way also, if a bug is caused by the ...
Lie Ryan's user avatar
  • 12.4k
1 vote

Is manually tagging content an ideal start for eventual machine learning?

If you have no other method of generating training data, then manually constructing them is the only way. After all, anything that isn't automatically done by a computer model is by definition "manual"...
Kilian Foth's user avatar
1 vote
Accepted

Can tags have values?

I think it might be better to keep tags and attributes separate. Attributes are usually name/value pairs and are often (in my experience) typed so that you can't enter the weight of a product as "blue"...
FrustratedWithFormsDesigner's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible