Comments (3)
Example Workflow
This workflow uses the official hashicorp action to working with Terraform in GitHub Action to send terraform fmt
corrections.
on:
pull_request_target:
types: [opened, synchronize]
branches:
- main
name: ci
jobs:
terraform-fmt:
runs-on: ubuntu-latest
env:
ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
steps:
- uses: actions/checkout@v2
with:
ref: ${{github.event.pull_request.head.ref}}
repository: ${{github.event.pull_request.head.repo.full_name}}
- uses: hashicorp/setup-terraform@v1
- run: terraform init
- name: Terraform Fmt
run: terraform fmt --recursive
- uses: googleapis/code-suggester@v1 # takes the changes from git directory
with:
command: review
pull_number: ${{ github.event.pull_request.number }}
git_dir: '.'
When a PR is sent with a "dirty" change, actions creates PR comments like so:
from emblem.
Exit criteria on this issue is:
- Guidelines on creating linter actions, including how to handle access tokens
- Documentation on actions/workflow tools that have been enabled
from emblem.
I recommend using black
and/or flake8
for Python files.
from emblem.
Related Issues (20)
- Update setup.sh to update breaking change introduced in `hashicorp/terraform-provider-google` v5 HOT 1
- api-unit-tests failing
- Resolve periodic `testing-web-e2e-trigger` failures due to kaniko cache
- break up `web-e2e.cloudbuild.yaml` into multiple steps HOT 1
- Bug: data ref `data.google_cloud_run_service.content_api` causing `setup.sh` build failure HOT 1
- Use built-in Cloud Build vars in e2e-testing module HOT 1
- Move `run.googleapis.com` service provisioning to bootstrap script HOT 1
- e2e-runner build in set up fails HOT 2
- Add smoke tests for the Content API
- Clean up Client app setup script and README instructions
- Modernize Cloud Build YAML with 'script' property HOT 1
- "argument named region not expected here" HOT 1
- Error creating Trigger: googleapi: Error 400: Repository mapping does not exist. HOT 6
- Make it easy for people to modify the content API to their own needs HOT 1
- Playwright dependency always fail testing
- in setup.sh, setting env vars via --update-env-vars is not always idempotent, it fails if a variable doesn't exist HOT 2
- Playwright dependency versions not all available on Renovate schedule HOT 1
- API Unit Tests are silently failing: Permission to write Cloud Trace telemetry HOT 4
- `ops/e2e-runner-build.cloudbuild.yaml` does not exist HOT 1
- Resolve persistent `api-unit-test` trigger failures blocking renovate-bot PRs
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from emblem.