Figure out a way to run cron builds on non-default branches without a PAT

Open
#6,051 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, github-actions
Domain
ci-cd, security

Research direction

Start by inspecting the scheduled build workflows and the SunPy organization secret setup described in the issue. Determine how cron builds currently target non-default branches and what GitHub-supported mechanism could remove the PAT; done means those builds run on non-default branches without the stored PAT.

Written by the indexing model from the issue text.

Description

Infrastructure Upstream Fix Required
Provide a general description of the issue or problem.

At the moment we have the situation where the @SunPyBot Github account has a PAT minted and stored in sunpy's org secrets to allow our scheduled build workflows to run.

This is nasty, fix it.

Dominant language
Python
Stars
1k
Forks
682
Avg merge
1d 17h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sunpy/sunpy

All issues in sunpy/sunpy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.