Skip to content
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

ci: bump document action for node20 #1076

Merged
merged 1 commit into from
Mar 17, 2024
Merged

ci: bump document action for node20 #1076

merged 1 commit into from
Mar 17, 2024

Conversation

csett86
Copy link
Collaborator

@csett86 csett86 commented Mar 16, 2024

No description provided.

Signed-off-by: Christoph Settgast <csett86_git@quicksands.de>
Copy link

what-the-diff bot commented Mar 16, 2024

PR Summary 🎉

💼 We've updated our CI workflow file!
Our Continuous Integration (CI) workflow, found in the file .github/workflows/ci.yml has been modified. This update results in more efficient and smoother operations on our GitHub repository. It's like greasing the wheels of a squeaky bike! 🚲

🔄 Improved an Automation Tool!
We updated an automation tool, DenverCoder1/doxygen-github-pages-action. Think of it like upgrading your favourite kitchen gadget with a fresh version—it's made things better! The new version, fondly referred to as 60e8d33d954eafb4d54710db8130fb0ad8f7d157, helps us sharpen our work even more. 🔧

📚 Documenting with Power!
This action uses our secret GitHub token and effortlessly deploys it to a 'branch' of the GitHub repository known as gh-pages. This is similar to a special, secure room where all important files are kept. The key result of this change is that it generates Doxygen documentation—an upgraded way to explain what our code does! It's as if your complex cooking recipe got suddenly easier to follow, thanks to a better explanation! 🥘

Let's see this in action and enjoy smoother workflows and better documentation, folks! Keep shining and innovating! 🌟💡🚀

@DSCaskey
Copy link
Contributor

Hey @csett86

I'm sure this is fine. I'm just trying to figure out what the change does (as the neccessary node bump was already made in doxygen-github-pages-action with your PR) and where does the string come from? Can I assume it's to use the current ver of doxygen-github-pages-action?

@csett86
Copy link
Collaborator Author

csett86 commented Mar 17, 2024

I am bumping the action version manually to a pinned commit (latest of that action), as the latest tagged version 1.3.0 does not have the fix yet, but is from 2023...

So the string comes from the commit history of the action in question

@csett86 csett86 merged commit 2319e10 into develop Mar 17, 2024
10 checks passed
@csett86 csett86 deleted the ci-document-bump branch March 17, 2024 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants