2 ms·
I feel like the biggest problem is they arent fetched by default, so you dont want to put anything important as half the people cloneing your repo wont see them
by bawolff 4y ago
I feel like the biggest problem is they arent fetched by default, so you dont want to put anything important as half the people cloneing your repo wont see them.
- quickthrower2 4y agoAll these bad defaults around notes, and Github not showing them. makes me worry it is defacto deprecated.
- jayd16 4y agoI feel like this is a good default if the idea is to cram in automation metadata.
- makeitdouble 4y agoYou're right, but then the name becomes misleading (it should be "Git Metadata" or something similar) The best way out of this situation could be aliasing the feature to something else with better defaults, with a hope that gets adopted by github/gitlab and the major GUIs
- jayd16 4y agoMaybe just give notes a namespace if it doesn't have it already. That way you can subscribe to some and not others.
- loeg 4y agoYou have your users add remote.origin.fetch='+refs/notes/*:refs/notes/*' to their git config and then they're fetched going forward, but yeah it's annoying that it isn't the default for a fresh clone.