-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add CI/CD workflows for Cloud Functions #190
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This (fake) test case was purposely done in order for Daniel to show me that the test would successfully run
LGTM, although I'm not super familiar with GitHub Actions :) |
on: | ||
workflow_dispatch: | ||
push: | ||
pull_request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need to include the pull_request
option if you already have push
enabled.
There are cases where both are necessary. E.g.,when triggering on pushes/PRs on specific branches. However, this is not one of those cases.
CODACY_PROJECT_TOKEN: ${{ secrets.CODACY_PROJECT_TOKEN }} | ||
|
||
|
||
codacy-coverage-reporter: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
codacy-coverage-reporter
must be indented with two spaces, not four.
The goal of this PR is to develop a CI/CD workflow that tests changes to any of the Pitt-Google Broker's microservices when triggered by the following actions:
I appreciate any feedback, as well as any references to documentation of best practices for future improvements.