@b0rk great information, as always! Thank you for creating and sharing!
Maybe interesting in that context: some time ago I experimented with what the most minimal .git for would look like and still be recognized by #git: https://manuel-strehl.de/minimal_git_folder
I'm unsure if signing my #Git commits is the best idea. When my #GPG key expires, commits will show on #Github as unverified. Should I stop signing my commits? I'm aware you can renew keys. However, if you no longer have access to the key, then it can't be renewed.
If a GPG key could no longer be retrieved, all commits signed with that key would appear as unverified, from what I understand.
Perhaps #boost for more visibility? :blobcatshrug:
Get the best out of #git and #sqlite by having your database versioned in a human-readable format:
# Create a local git repo and a db file
$ git init
$ sqlite3 ./test.db
sqlite> create table test(id int primary key, value text);
$ git add test.db
# Set the diff format for *.db files
$ git config diff.sqlite3.binary true
$ git config diff.sqlite3.textconv "echo .dump | sqlite3"
$ echo '*.db diff=sqlite3' >> .gitattributes
# Do some stuff with the db
$ sqlite3 ./test.db
sqlite> insert into test values(1, 'a');
sqlite> insert into test values(2, 'b');
sqlite> insert into test values(3, 'c');
sqlite> update test set text = 'aaa' where id = 1;
sqlite> delete from test where id = 3;
# Check the diff
$ git diff
diff --git a/test.db b/test.db
index 9d6e6db..c9a7a08 100644
--- a/test.db
+++ b/test.db
@@ -1,4 +1,6 @@
...
CREATE TABLE test(id int primary key, text text);
+INSERT INTO test VALUES(1,'aaa');
+INSERT INTO test VALUES(2,'b');
COMMIT;
A surprisingly common mistake people do when contributing to #OpenSource projects is to forget the (often required) sign-off on their commit, and then close the PR only to open a new one where the sign-off is included. This isn’t needed! Next time, just:
git commit --amend --signoff
git push --force
And your signoff will be added to the commit in your PR.
Wir suchen #Rust#Entwickler. Anfangs als #teilzeit aber sehr sehr wahrscheinlich wird das zu #Vollzeit wachsen (oder mehrere Teilzeit, wenn das besser passt).
Ort: Voll #Remote - wir haben kein Büro mehr - aber aus vertraglichen und rechtlichen Gründen muss der Arbeitsort innerhalb von .de liegen.
Selten (derzeit einmal im Jahr) eine Fahrt in die Gegend um Frankfurt/Main einzuplanen, Firmenevent.
Nötig: Gute #Rustlang Kenntnisse. Und man sollte andere Sprachen (viel C, etwas Java, Bash) zumindest grob lesen können.
Es geht ums (Neu/Um)schreiben von Applikationen.
Außerdem Umgang mit #git/#gitlab nötig - und wir sind voll #linux basiert.
My this year’s holiday gift to maintainers so they have something to link to, and to contributors so they don't make a painful mistake in the first place:
#sxmo#linuxmobile news:
i fixed the wifi-sec hotspot creation bug, added a 'GSM Disable' entry and a 'Wifi Credentials' to show pw in text and qr-code of the connected wifi or hotspot.
and:
i decided to stop messing with sourcehut, #git send-email and upstream, for fuck sake, its so demotivating! to which email address? why did it not only send the last commit? where is it gone?
i prefer to use my time for features/fixes and to document them, not to messup pipelines of others....
'"[…] introduces preliminary support for a new reference storage backend called “reftable,” promising faster lookups, reads, and writes for repositories with any number of references. […]
Preliminary support for SHA-1 and SHA-256 interoperability
[…] git config learned a new option to help document your .gitconfig file […]"'