Remove hard-coded organization in website build action #157
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is this PR
Why is this PR needed?
This repository is a cookiecutter template, but the docs build workflow hard-codes the neuroinformatics-unit organization. This prevents scheduled workflows from running correctly for downstream users who generate projects from this template.
What does this PR do?
Removes the hard-coded organization check from the GitHub Actions condition and instead restricts scheduled runs to the main branch only. This preserves safety while making the workflow reusable for any repository owner.
References
Fixes #125
How has this PR been tested?
The change is limited to a GitHub Actions conditional. The logic was verified by inspecting the workflow condition and ensuring it behaves identically for non-scheduled events while enabling scheduled runs for downstream repositories.
Is this a breaking change?
No
Does this PR require an update to the documentation?
No
Checklist: