GHCR

[crayolakat]

Description

StateVoices currently doesn't have GHCR set up on their GitHub organization, so the GH Action to build a Spoke Docker image fails.

Since MoveOn has their own separate branch, we should be pushing to our own GHCR anyway, not overwriting StateVoices every time we do a push on main.

Checklist:

• I have manually tested my changes on desktop and mobile
• The test suite passes locally with my changes
• If my change is a UI change, I have attached a screenshot to the description section of this pull request
• My change is 300 lines of code or less, or has a documented reason in the description why it’s longer
• I have made any necessary changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• My PR is labeled [WIP] if it is in progress

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[codygordon]

Navigating to ghcr.io/moveonorg/moveon-spoke I get a 404, but ghcr.io/moveonorg/spoke works – is that what it should be?

[crayolakat]

[Pasting here for visibility to the open-source community]

The ghcr.io/moveonorg/moveon-spoke URL should exist once the branch is merged into main since the workflow is run when a push is made on the main branch. I had to create a new ghcr.io/moveonorg/moveon-spoke URL and could not longer push to the old ghcr.io/moveonorg/spoke URL (403 forbidden error). I believe it's because this MoveOnOrg/Spoke is actually a new forked repo from the StateVoicesNational/Spoke repo, so lost the permissions to push to ghcr.io/moveonorg/spoke