Skip to content

api-tracking#498

Merged
jirhiker merged 1 commit intostagingfrom
api-tracking
Feb 12, 2026
Merged

api-tracking#498
jirhiker merged 1 commit intostagingfrom
api-tracking

Conversation

@jirhiker
Copy link
Copy Markdown
Member

Why

This PR addresses the following problem / context:

  • Use bullet points here

How

Implementation summary - the following was changed / added / removed:

  • Use bullet points here

Notes

Any special considerations, workarounds, or follow-up work to note?

  • Use bullet points here

Copilot AI review requested due to automatic review settings February 12, 2026 23:26
@jirhiker jirhiker merged commit da62def into staging Feb 12, 2026
10 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR corrects the configuration of APITALLY_CLIENT_ID in the GitHub Actions deployment workflows by changing it from a secret to a variable. This aligns with best practices where client IDs (which are not sensitive) are stored as variables, while client secrets remain as secrets.

Changes:

  • Changed APITALLY_CLIENT_ID from secrets to vars in both staging and production deployment workflows

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/CD_staging.yml Updated APITALLY_CLIENT_ID to use vars instead of secrets for staging deployments
.github/workflows/CD_production.yml Updated APITALLY_CLIENT_ID to use vars instead of secrets for production deployments

@TylerAdamMartinez TylerAdamMartinez deleted the api-tracking branch February 26, 2026 18:25
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.

2 participants