Timeline for GitHub Versioning - Organizing Structure
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2022 at 15:38 | comment | added | TalinTheDev | So, basically, tags are read-only branches... without being branches? Oof | |
| Feb 1, 2022 at 15:36 | comment | added | Bart van Ingen Schenau | @TalinTheDev, Yes. a tag gives a user-friendly name to a particular commit. The tag remains with that commit, even when more changes are added to the branch(es) that the commit is a part of. | |
| Feb 1, 2022 at 15:33 | comment | added | TalinTheDev | Ok so I think this is what I needed. Please let me know if my understanding of tags is correct. Once I tag the master branch as the release number (version number), people can still go back to the old versions right? | |
| Feb 1, 2022 at 15:28 | vote | accept | TalinTheDev | ||
| Feb 1, 2022 at 3:42 | history | answered | Mike | CC BY-SA 4.0 |