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
Description: Provide a brief background and justification for this issue
Using git's pre-commit checks, ensure linters are auto-run before commit/push cycle.
Acceptance Criteria: Create a list of functional outcomes that must be achieved to complete this issue
Allow linting errors in commits for but not pushes.
Configuration document for developers is produced
Secrets checks run before commits are allowed
Testing Checklist has been run and all tests pass
README is updated, if necessary
Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
Investigate git commit/push file actions
Investigate git secrets catches sendgrid api per recent events
Run Testing Checklist and confirm all tests pass
Notes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this
Supporting Documentation: Please include any relevant log snippets/files/screen shots
Open Questions: Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete
The text was updated successfully, but these errors were encountered:
andrew-jameson
changed the title
[DRAFT] As a developer, I want linters to run before git push
As a developer, I want linters to automatically run before git push
May 31, 2022
andrew-jameson
changed the title
As a developer, I want linters to automatically run before git push
As a developer, I want linters to run automatically before git push
May 31, 2022
Description:
Provide a brief background and justification for this issue
Using git's pre-commit checks, ensure linters are auto-run before commit/push cycle.
Acceptance Criteria:
Create a list of functional outcomes that must be achieved to complete this issue
Tasks:
Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue
Notes:
Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this
Supporting Documentation:
Please include any relevant log snippets/files/screen shots
Open Questions:
Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete
The text was updated successfully, but these errors were encountered: