Skip to content

The Standardize CI (tier: unimportant) has been adding pkgdown actions to private repos #32

Description

@aylapear
  • Private repos should not have a public website so they shouldn't have a pkgdown action.
  • Our current pkgdown actions in this will deploy if the right settings are ticked in the repo settings, for example I found 1 repo that had a deployed public repo that was a private internal package.
  • If the deploy branch isn't set then the public website won't deploy and thus is just a waste of action minutes as well as confusing.

I would recommend that private repos do not get the pkgdown action. Unsure of how to make sure this is enforce when these batch standardized CI PRs go out.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions