A clean Git history is the key to successful teamwork and quick bug fixes. Errors can only be successfully tracked down if it is always possible to trace when and where code was changed by whom and for what reason.
🥴 However, in the rush of the battle, the changes that are packaged in a commit are sometimes not taken very seriously. Who has never experienced this? A change that is actually unrelated to the current work package has made it into the commit because the file has already been saved temporarily.
💡The solution: With an "interactive add" (git add -i), you can pack partial changes ("hunks") into a commit and specify line by line what should be included in the next commit.
Sometimes, there might be a need to save a document in its current form before making alterations. DEVONthink provides a clever method to create versions of a document automatically. Learn more about this feature here. #devonthink#pkm#versioning#workflowhttps://buff.ly/3K05dV1
On Foojay :foojay: Today, @frankel of #ApacheAPISIX describes the options for #versioning HTTP APIs: path-based, query-based, and header-based. Check them out and be consistent across your organization:
I am looking for good examples of using online version control systems to formulate and maintain rules, codes and laws in a transparent & participatory way.
We have an interesting conversation with an #anarchist#historian friend, which may lead towards new approach to co-creation of a social dynamics inside and among collectives.