Conversation
|
I kind of like it 😂 You mean a pre-commit hook, right? As long as it's not flaky, yep, why not. We can also add a meta-test specifically for that, as you wish. Maybe that's easier than a pre-commit hook. |
Ah, yes. I do mean a pre-commit hook. I realise I missed writing that in the PR description after the word "custom" 😅 Let me explore if a meta-test is easier/better; maybe it is. That said, the linters are not running in this PR. Could you please install the pre-commit.ci app to this repository for me? |
|
I spent some time adding a meta-test of sorts that runs a bunch of checks for the provenance data. This was a bit tedious, so agentic coding tools came in a bit handy here. However, I am aware that there is a bit more code than we'd imagine – we could loosen the validations a bit, if you'd like. I kind of like this a bit better than having a pre-commit hook, since it's executed with the tests. |
This PR updates the provenance metadata for all tests. We now record provenance as a structured object that includes the test's node ID, the commit hash, and a direct URL to the relevant source lines in https://github.com/conda/conda/.
AI disclosure
I quickly realised after updating a few test file links manually that this was going to be a tedious task, so the update (see the second commit) was performed by a script that Claude Code, using the Sonnet 4.6 model, wrote upon my asking. Here is the script:
We could restructure the above script into a custom pre-commit hook manually, so that I don't have to come back to it again and do all of this later. Thoughts, @jaimergp?