I have always had this problem with hooks and new contributors: since hooks don't run by default if you just clone the repository, my open source projects get many PRs from new contributors that did not run the linting and commit hooks. I understand there's a security reason for this but what workflows have worked best for you to get everyone to run the hooks? And do you think the new config-based hooks can help new contributors?
sethops1 14 minutes ago [-]
> what workflows have worked best for you to get everyone to run the hooks
By running the linters and any other checks on CI instead.
baq 10 minutes ago [-]
autoformatter and autofix linter results can be committed and pushed by CI into the PR branch itself. this is a pain sometimes, but as a repo owner it should protect your sanity.
skydhash 1 minutes ago [-]
I just add a check workflow that test that the files are well formatted and linted. If it passes, one of the key things I check are changes to the configuration. Some tools allows for bypass comments, so I keep an eye out for those too.
ajoberstar 2 days ago [-]
Nice to see some seemingly jujutsu inspired features getting into Git core.
git history reword ~= jj describe
git history split ~= jj split
Not familiar with jj and don't want to get into bike shedding, but how is describe supposed to be a good name for history rewrites?
auscompgeek 1 minutes ago [-]
describe is also the command you can use to edit the commit message of the change you're currently drafting. In jj there's no staging area, every modification to the working tree immediately gets integrated into the current commit. (This means if you have no diff in your working tree, you're actually on an empty commit.)
5 minutes ago [-]
roblabla 10 minutes ago [-]
jj describe gives a name to a commit. In jj, everything rewrites the history, so there's no real point in calling it out in the command name since it's just the default behavior.
skydhash 7 minutes ago [-]
Not really familiar too, but jj has everything committed by default (no index, staging area, and uncommitted changes). You use ‘jj new’ to stop adding changes to the current commit.
‘jj describe’ lets you add a message to a commit as it’s not there by default.
samtrack2019 3 days ago [-]
the new git history command seems to be useful for quick reword, altho since i use lazygit/magit i don't really see much of a problem to me
olejorgenb 12 minutes ago [-]
Wish reword took a commit range though
Rendered at 12:28:47 GMT+0000 (Coordinated Universal Time) with Vercel.
By running the linters and any other checks on CI instead.
https://www.jj-vcs.dev/latest/cli-reference/#jj-describe
https://www.jj-vcs.dev/latest/cli-reference/#jj-split
‘jj describe’ lets you add a message to a commit as it’s not there by default.