Add workflow templates, property files, and icons#1
Conversation
This change adds basic workflow templates for cf.gov satellite apps frontend and backend CI and releases, Python libraries, and MkDocs publishing to GitHub. It also adds a README with some basic information about how to use the templates and what they are.
| ## consumerfinance.gov-specific workflow templates | ||
|
|
||
| - [cfgov-frontend-ci.yml](workflow-templates/cfgov-frontend-ci.yml): A frontend CI workflow template for cf.gov satellite apps. | ||
| - [cfgov-python-satellite-ci.yml](workflow-templates/cfgov-python-satellite-ci.yml): A backend CI workflow template for cf.gov satellite apps based on tox. |
There was a problem hiding this comment.
What would you think about reframing these as general front-end/back-end CI workflows? They offer what we would consider to be best practices for any CFPB project.
There was a problem hiding this comment.
We can do that...it felt somewhat presumptuous to me to do that (at least on the backend because it presupposes Python).
There was a problem hiding this comment.
You can word it in such a way that it doesn't. Maybe instead of calling them frontend/backend, it should be JavaScript/Python?
There was a problem hiding this comment.
@Scotchester looking at this again, I'm fine moving cfgov-frontend-ci to cfpb-javascript-ci, but I think I'd like to keep the distinction between cfgov satellites and Python libraries, even if the only difference is the default of including Django in the tox matrix.
2 participants
This change adds basic workflow templates for cf.gov satellite apps frontend and backend CI and releases, Python libraries, and MkDocs publishing to GitHub.
It also adds a README with some basic information about how to use the templates and what they are.