Skip to content

Create staging.yaml - #200

Open
binamkayastha wants to merge 1 commit into
masterfrom
create-staging
Open

binamkayastha wants to merge 1 commit into
masterfrom
create-staging

Conversation

@binamkayastha

@binamkayastha binamkayastha commented Oct 11, 2026 •

Copy link
Copy Markdown
Collaborator

Creation of every 4 hours to run on the staging branch. This way we can merge prs into the staging branch and it will run every 4 hours on all the test accounts

# Separate job so the elevated token never coexists with the posting steps.
# Shares the pages-publish concurrency group with deploy-pages.yml, so the
# two can no longer deploy Pages at the same time.
publish-redirects:

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@flufflycthu1u Is this safe to have on the staging.yml?

with:
# Scheduled runs always execute on the default branch, so check out
# the staging branch's code explicitly.
ref: staging

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This is how the yaml works - it will checkout the staging yaml and run the program on it

BLUESKY_HANDLE: ${{ secrets.BLUESKY_TEST_HANDLE }}
BLUESKY_PASSWORD: ${{ secrets.BLUESKY_TEST_PASSWORD }}
MASTODON_TOKEN: ${{ secrets.MASTODON_TEST_TOKEN }}
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

These are all the test accounts

This branch has not been deployed

No deployments
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.

1 participant