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

Force specific hash when building a single docs branch #44204

Open
philwebb opened this issue Feb 11, 2025 · 0 comments
Open

Force specific hash when building a single docs branch #44204

philwebb opened this issue Feb 11, 2025 · 0 comments
Labels
type: task A general task
Milestone

Comments

@philwebb
Copy link
Member

Currently when a docs build is triggered for a branch, the latest version of that branch will always be used. This can cause problem if a subsequent build adds meta-data and hasn't completed in time.

This happened with commit f5f888d which triggered a docs build that actually used afcc780.

If we pass the sha in when we trigger the build, we should be able to git reset the branch before starting Antora.

@philwebb philwebb added this to the 3.3.x milestone Feb 11, 2025
@philwebb philwebb added the type: task A general task label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

1 participant