Automate doxygen builds #521
No reviewers
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi!521
Loading…
Reference in a new issue
No description provided.
Delete branch "automate-doxygen-builds"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
resolves #5
doxygen -udoxygen/main_page.mdfile as the generated site's main page.gh-pagesbranch for deployment (only for push events to the master branch).Admin prep
The required preparation needed from admins is
gh-pagesbranch root folder as source of deployments.I realize that there is already a branch named
github_pages, but I think that branch was meant for a different purpose. The branch published to github pages typically only has the site's HTML resources (not any programming or documentation sources) -- especially when using Doxygen as the static site generator.Alternatively (or additionally), a link could be added to the README in the "What does the API look like?" section.
I've made a job on master branch, to test CI in this PR.
As for other changes/requests - I'll get to it tiny bit later. Too much preoccupied at the moment.
The branch used to publish the docs' site can be configured (see here) Default is a branch named
gh-pages.@ -0,0 +1,13 @@# HIDAPI Doxygen outputupdate links
@ -103,10 +105,11 @@#ifdef __cplusplusas per agreement - we use only
/** c-style comments */- for consisteny@ -16,0 +54,4 @@uses: peaceiris/actions-gh-pages@v3with:github_token: ${{ secrets.GITHUB_TOKEN }}publish_dir: ./docsI don't think the history of documentation changes has any value in the branch, given that all doc sources are in the repo anyway
originally it was created for the same purpose as a playground
we just didn't make it right to the end
at this moment I believe it is time to get rid of it
@ -16,0 +43,4 @@concurrency:group: "github-pages-deploy"cancel-in-progress: truesteps:lets make sure to deploy only the latest
@ -0,0 +1,13 @@# HIDAPI Doxygen outputOops! 😆
@ -103,10 +105,11 @@#ifdef __cplusplusOh, I couldn't find any code style guideline, but I didn't look very hard...
@ -103,10 +105,11 @@#ifdef __cplusplusdone. The
<is required as part of doxygen trailing docstring syntax.This is the important part that allows eliding specific members from the generated docs. ✏️ Here, I used it to exclude the "helper macros" that don't have a docstring.
@ -103,10 +105,11 @@#ifdef __cplusplusunfortunately those aren't written anywhere
just the fact of consistency
@ -0,0 +1,13 @@# HIDAPI Doxygen outputThis site is dedicated to hosting an [API reference for the HIDAPI library](#API).I'm not sure where
#APIlink points to@ -0,0 +1,13 @@# HIDAPI Doxygen outputThis site is dedicated to hosting an [API reference for the HIDAPI library](#API).ah, I see - that's a Doxygen link