You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today when user submits a pull request to professional services repo, lint checks are executed via cloud build trigger inside google cloud project owned by repo maintainers. In case of failures, PR authors do not have visibility for the failure reasons.
To resolve this we have recommendation in Contribution section to run local lint checks. But this process has multiple steps and dependencies on terraform and docker to be available.
Proposal
Build a linitchecker.yaml that PR author can run locally using single gcloud command without need for terraform and docker
Run the gcloud command: gcloud builds submit --config lintchecker.yaml .
If we are planning to move forward with dynamic cloud build, rebase checks can also be included so that author has complete visibility on all the checks before PR submission
The text was updated successfully, but these errors were encountered:
Issue
Today when user submits a pull request to professional services repo, lint checks are executed via cloud build trigger inside google cloud project owned by repo maintainers. In case of failures, PR authors do not have visibility for the failure reasons.
To resolve this we have recommendation in Contribution section to run local lint checks. But this process has multiple steps and dependencies on terraform and docker to be available.
Proposal
Build a linitchecker.yaml that PR author can run locally using single gcloud command without need for terraform and docker
#linitchecker.yaml
Run the gcloud command:
gcloud builds submit --config lintchecker.yaml .
If we are planning to move forward with dynamic cloud build, rebase checks can also be included so that author has complete visibility on all the checks before PR submission
The text was updated successfully, but these errors were encountered: