Skip to content

ci: stop building pkgdown on forks #346

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

Merged
merged 2 commits into from
Nov 15, 2023
Merged

Conversation

dsweber2
Copy link
Contributor

This makes it so that pkgdown will only run if the repo is owned by cmu-delphi directly. I'd rather pkgdown stopped trying to run on my fork whenever I sync it with main or dev, causing failing build notifications. This should solve it, taken from here, and working on epidatr.

this makes it so that pkgdown will only run on branches owned by cmu-delphi directly
Copy link
Contributor

@brookslogan brookslogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I thought that this type of CI would automatically not run on forks. Right now our workflow is to have branches off of the cmu-delphi repo rather than in forks; LMK if you are lacking permissions.

todo: please add on to the line 4 comment to describe this change. [Feel free to merge after.]

@dsweber2
Copy link
Contributor Author

Added. Apparently this needs approval from both you and @dajmcdon? Y'all may want to make that either, rather than both, for future pull requests.

I currently can't add branches directly to epiprocess or epipredict

@dshemetov dshemetov merged commit 9165bcc into cmu-delphi:main Nov 15, 2023
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.

3 participants