Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(PR-41): add a shared CI standard checks workflow #66

Merged
merged 8 commits into from
Jan 10, 2024

Conversation

miquelarranz
Copy link
Contributor

@miquelarranz miquelarranz commented Jan 8, 2024

Add a new workflow for CI standard checks. We will use it to use the 50k free minutes we have with Github.

https://typeform.slack.com/archives/CCWDN8ASJ/p1704726455798989

@miquelarranz miquelarranz requested a review from a team as a code owner January 8, 2024 15:36
macabu
macabu previously approved these changes Jan 8, 2024
Copy link
Contributor

@macabu macabu left a comment

Choose a reason for hiding this comment

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

OCD intensifies

.github/workflows/ci-standard-checks-workflow.yaml Outdated Show resolved Hide resolved
jobs:
ci-standard-checks:
runs-on:
- ubuntu-latest
Copy link
Contributor

Choose a reason for hiding this comment

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

:chefs-kiss: This is the most important part of the change, now using GH hosted runners for this workflow

Co-authored-by: Matheus Macabu <macabu@users.noreply.github.com>
zdenekkostal
zdenekkostal previously approved these changes Jan 8, 2024
@davidsalvador-tf
Copy link
Contributor

The value used for githubToken will be secrets.GITHUB_TOKEN (which is a better option than GH_TOKEN) for every repo using this workflow, great! 🚀

- name: CI Standard Checks
uses: Typeform/ci-standard-checks@v1
with:
githubToken: ${{ secrets.GH_TOKEN }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that for this use case we can use the token with minimum privileges that is generated per repository (GITHUB_TOKEN) instead of this Organization wide secret GH_TOKEN which corresponds to a PAT from a user with lots of privileges. See GitHub's security hardening guidelines.

Suggested change
githubToken: ${{ secrets.GH_TOKEN }}
githubToken: ${{ secrets.GITHUB_TOKEN }}

Copy link
Contributor

Choose a reason for hiding this comment

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

Fixed, thanks!

@miquelarranz miquelarranz merged commit 6ea8ad7 into main Jan 10, 2024
1 check passed
@miquelarranz miquelarranz deleted the PR-41_shared_ci_standard_checks_workflow branch January 10, 2024 11:58
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.

4 participants