-
Notifications
You must be signed in to change notification settings - Fork 46
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
Updating build process and gh-pages fork publications #568
base: main
Are you sure you want to change the base?
Conversation
@JonathanGregory I’m integrating technical changes to build the documents and publish artifacts on the |
Thanks, @cofinoa. As you know, I don't speak this language! You may be the only fluent speaker. However, as far as I can tell, it looks fine. I think it would be good to have an issue (labelled |
@JonathanGregory I have opened a related issue #569 to this PR |
…onment variables - Introduced environment variables for desired branch, path, and build type: - DESIRED_BRANCH: "gh-pages" - DESIRED_PATH: "/" - DESIRED_BUILD_TYPE: "legacy" - Simplified configuration management for GitHub Pages enforcement. - Improved maintainability by reducing hardcoded values across steps. - Ensured dynamic usage of environment variables in branch creation, artifact handling, and GitHub Pages setup.
- Skip `build_docs` job when the pull request event type is `closed`. - Add `cleanup_docs` job to remove associated artifacts from the `gh-pages` branch for closed PRs. - Ensure `publish_docs` job depends on `build_docs` and skips execution for closed PRs. - Refine `TARGET_DIR` logic for PR previews to ensure proper organization. - Improve workflow efficiency by avoiding unnecessary builds and deployments.
No issue for discussion of these changes.
Release checklist
cf-conventions.adoc
? Add in two places: on line 3 and under.Additional Authors
inAbout the authors
.cf-conventions.adoc
up to date? Versioning inspired by SemVer.history.adoc
up to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then,
main
always is a draft for the next version.