-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tools: provide tool to create doxygen maintainer list #21062
Conversation
... rather than outdated wiki page.
187b795
to
4b31bfd
Compare
That did not work. :-( @RIOT-OS/ci can you have a look? |
I don't know how that new html is created or where it ends up, but these lines deal with the preview: https://github.com/RIOT-OS/murdock-scripts/blob/931a4136b6efa7d44539826d665ae2b1561e16e1/build.sh#L281 |
This is just the generated result from RIOT-OS#21062 while that PR is under development
This is just the generated result from RIOT-OS#21062 while that PR is under development
This is just the generated result from RIOT-OS#21062 while that PR is under development
eee5863
to
5fe56c7
Compare
5fe56c7
to
83b01c8
Compare
This is just the generated result from RIOT-OS#21062 while that PR is under development
This is just the generated result from RIOT-OS#21062 while that PR is under development
https://github.com/RIOT-OS/RIOT/actions/runs/12201211174/job/34039104721 is failing for this PR since the build was initiated from my fork (where the secret is not present). However, I did some testing on a feature branch. There it worked: https://github.com/RIOT-OS/RIOT/actions/runs/12200980590 |
Provided RIOT-OS/riot-os.org#141 which might be a better alternative |
Closing in favor of RIOT-OS/riot-os.org#141 |
Contribution description
This has been long discussed, but never set into action. Given that MAINTAINING.md now references a non-existent wiki page (which was outdated before its deletion), I say it is about time.
This basically takes the information from the RIOT-OS org teams and combines it with the information in CODEOWNERS. Caveat: One needs a token with read:org permission to get the teams.
I tried to match the CODEOWNERS patterns to doxygen groups somehow, but there either too little overlap (only @jia200x who chose documentation as an area of expertise had matching doxygen groups) or too much (e.g., @kaspar030 then received nearly every CPU, because he is interested in
pm.c
which have an@ingroup
for each respective CPU or theirperiph
interface...), so I just gave up on that.Testing procedure
If all goes well, Murdock should just have a new
maintainers-list.html
in its Documentation preview.Issues/PRs references
None so far.