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

[CI/CD Improvements] Standardize and automate formatting for workflows #137

Open
3 tasks
Tracked by #74
mikealfare opened this issue Aug 7, 2024 · 0 comments · May be fixed by #141 or #143
Open
3 tasks
Tracked by #74

[CI/CD Improvements] Standardize and automate formatting for workflows #137

mikealfare opened this issue Aug 7, 2024 · 0 comments · May be fixed by #141 or #143
Assignees
Labels
community This PR is from a community member cost_reduction

Comments

@mikealfare
Copy link
Contributor

mikealfare commented Aug 7, 2024

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt-postgres functionality, rather than a Big Idea better suited to a discussion

Describe the feature

As a maintainer, I want to automate formatting checks, so that I can focus more on content in PRs and still maintain a code quality standard.

Acceptance Criteria

Formatters:

Linters:

Style standards:

  • Job ids, step ids, and variables are in kebab case
  • Job names, step names, and description fields follow dbt docs standards (capitalize first word only)
  • Extra descriptors should be avoided unless required for disambiguation, e.g.
    • version-number -> version
    • archive-name -> archive
  • Workflow files use a four space tab
  • Scripts (inline or separate files) use environment variables in env instead of inline substitution like ${{ inputs.value }}
@mikealfare mikealfare added enhancement New feature or request triage tech_debt and removed enhancement New feature or request triage labels Aug 7, 2024
@mikealfare mikealfare added cost_reduction community This PR is from a community member and removed tech_debt labels Aug 7, 2024
@mikealfare mikealfare self-assigned this Aug 9, 2024
@leahwicz leahwicz linked a pull request Aug 12, 2024 that will close this issue
4 tasks
@leahwicz leahwicz linked a pull request Aug 30, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community This PR is from a community member cost_reduction
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant