zeroiee, to programming
@zeroiee@techhub.social avatar

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.

:git: "Staging patches": https://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging

devontechnologies, to random
@devontechnologies@devontechnologies.com avatar

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. https://buff.ly/3K05dV1

image/jpeg
image/jpeg
image/jpeg

mamund, to TierraSapiens
@mamund@mastodon.social avatar

(@dret) and I have been delivering our workshop. The discussion topic of comes up and, though we only touch on it in the workshop, here's a pointer to my ("The Modifiability Problem") https://buff.ly/3JDNSAW

Here's my on the subject, too: https://buff.ly/49Xy6vE

image/jpeg

thezerobit, to programming
@thezerobit@anticapitalist.party avatar

For API developers: what's your API versioning strategy?

Please respond with a description. A poll would be useless as there are as many versioning strategies as there are stars in the night sky.

#API #programming #versioning

foojay, to random
@foojay@foojay.social avatar

On Foojay :foojay: Today, @frankel of describes the options for HTTP APIs: path-based, query-based, and header-based. Check them out and be consistent across your organization:

https://foojay.io/today/api-versioning/

8petros, to philosophy Polish

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 friend, which may lead towards new approach to co-creation of a social dynamics inside and among collectives.

Proof of concept needed.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • magazineikmin
  • osvaldo12
  • GTA5RPClips
  • mdbf
  • Youngstown
  • tacticalgear
  • slotface
  • rosin
  • kavyap
  • ethstaker
  • everett
  • khanakhh
  • JUstTest
  • DreamBathrooms
  • InstantRegret
  • cubers
  • normalnudes
  • Leos
  • ngwrru68w68
  • cisconetworking
  • modclub
  • Durango
  • provamag3
  • anitta
  • tester
  • lostlight
  • All magazines