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

configure workflow based on zap search #1258

Closed
wants to merge 7 commits into from
Closed

configure workflow based on zap search #1258

wants to merge 7 commits into from

Conversation

horatiorosa
Copy link
Contributor

Copy link

netlify bot commented Sep 13, 2024

Deploy Preview for applicant-portal canceled.

Name Link
🔨 Latest commit b6a064c
🔍 Latest deploy log https://app.netlify.com/sites/applicant-portal/deploys/66f1ac32ff317d00078d07d2

.github/workflows/production.yml Show resolved Hide resolved
- main
pull_request:

jobs:
Copy link
Collaborator

Choose a reason for hiding this comment

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

@TangoYankee @horatiorosa Maybe this is something we visit but would it be difficult to move these code quality checks into the workflows for deploying the environments? I much prefer things like code quality and tests being in the same workflow as deployments, as separate "jobs". That way you have the option of blocking the deployment if the code quality checks fail. We use this approach in EDDE's workflows.

Copy link
Member

Choose a reason for hiding this comment

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

yes and no to the difficulty question. We can just copy and paste the code quality checks into each environment workflow.

Long term, we should make the jobs reusable, otherwise we end up needing to update code across several workflows every time we make an updated. Of course, this goes for code quality and deployment jobs (we're mostly reusing code across the deployment workflows, too)

For now, would you like to go forward with copying and pasting code quality checks into each deployment workflow?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Yes please.

@TangoYankee TangoYankee force-pushed the main branch 2 times, most recently from 8334d77 to 344510d Compare September 17, 2024 14:58
Support deployments from main
Deploy to heroku and netlify from github actions
Require code quality checks to pass before deploying
Fix linting errors to pass quality checks

closes #1244

Co-authored-by: horatio <[email protected]>
nvmrc and node engine are updated to 20 in server

closes #1241
horatiorosa and others added 5 commits September 24, 2024 15:04
Protect server and client self service feature with flag

closes #1242

Co-authored-by: tangoyankee <[email protected]>
Bumps [express](https://github.com/expressjs/express) from 4.17.1 to 4.21.0.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/4.21.0/History.md)
- [Commits](expressjs/express@4.17.1...4.21.0)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [handlebars](https://github.com/handlebars-lang/handlebars.js) from 4.7.6 to 4.7.8.
- [Release notes](https://github.com/handlebars-lang/handlebars.js/releases)
- [Changelog](https://github.com/handlebars-lang/handlebars.js/blob/v4.7.8/release-notes.md)
- [Commits](handlebars-lang/handlebars.js@v4.7.6...v4.7.8)

---
updated-dependencies:
- dependency-name: handlebars
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.13.0 to 1.15.9.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](follow-redirects/follow-redirects@v1.13.0...v1.15.9)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
@TangoYankee
Copy link
Member

Closing because we put these changes on the "default" branch by making main the "default"

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.

Implement deployments and development from main
3 participants