Closed renghardt closed 2 years ago
I'm sorry you had to go through all of that. I didn't really realize just how awkward this experience might be.
Conveniently, this draft uses krandowm-rfc, so make update-venue
likely would have worked for you, with a fair bit less effort involved.
Thanks, I had no idea make update-venue
existed, and I wasn't aware of the "make update-* features" in general. That would be a good addition to the documentation for the tools. :slightly_smiling_face:
(I found that the CODEOWNERS file does say that it can be regenerated with make update-codeowners
- I wonder if a similar comment could be added to other places where things can be regenerated. In case of the .note.mk, I had no file to start with - but I did look at Spencer's file and wondered how he generated it.)
https://github.com/martinthomson/i-d-template/blob/main/doc/UPDATE.md is a start on documenting that.
It took me a while to figure out, but this PR adds a "Discussion venues" section to the draft, pointing to the Github repo and mailing list.
For future reference, what I recall doing was:
cd lib && git pull
to update the template repomake
, and then switch to using a "main" branch as advised by the outputmake -f lib/setup.mk
(which creates a commit)make clean && make
-> Finally, the "Discussion venues" section shows up in the generated .txt and .html fileMaybe there was an easier way to "update" a draft that was started before this feature existed, but I did not find it.