-
Notifications
You must be signed in to change notification settings - Fork 3
Conversation
Add GitHub action caching of pre-commit hooks and pip packages.
Migrate CI system and Docker Hub organization
Add missing env variable for test
…thon Set a default language for pre-commit hooks
…provement/upstream
Improvement/upstream
Add codeowners file with team OIS maintainers.
…provement/codeowners
Improvement/codeowners
Add isort configuration file.
Add isort tool to pre-commit hooks.
A user forked cisagov/scan-target-data and created a pull request, but the required GitHub Action(s) did not run. This is presumably because the user does not have Actions enabled in his or her fork. Ideally, the required Action(s) would run in cisagov/scan-target-data when a PR to merge changes back is created. Based on my reading of this link, adding the "pull_request" event type should make this happen: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#pull-request-events-for-forked-repositories
…m-forked-repos Make workflow run when a PR is opened, synchronized, or reopened
…ent/upstream-changes
@dav3r Are we able to disable the LGTM analysis: Python on this repo? |
Yes, I will disable it for now. Can you please remind me to re-enable it after this PR is merged? |
I can, but why does it need to be re-enabled when this isn't a Python project? |
I just checked and none of the checks are required for merging yet, so don't worry about LGTM failing for now. |
In this case, LGTM will still be checking the requirements files and the Python code in the |
Sounds good. I'll see if I can get it to succeed. |
If you can't, don't sweat it too much on this PR. We have seen it behave in weird ways when it is initially integrated to a project, but tends to work after that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @zenine07! I requested only a couple of changes.
src/secrets/quote.txt
Outdated
@@ -0,0 +1 @@ | |||
There are no secrets better kept than the secrets everybody guesses. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this file being used here? If not then it should be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
README.md
Outdated
@@ -70,6 +70,6 @@ Remove containers: | |||
|
|||
Angular app located at [localhost:4200](http://localhost:4200) | |||
|
|||
### Run pre-commit: | |||
### Run pre-commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We generally do Markdown headings ## Like this ##
with trailing octothorpes. Can you make this change throughout this file?
I'm also confused as to why the linters aren't checking this file. @mcdonnnj?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have anything auto-formatting on Markdown files. We would need to expand the markdownlint
configuration to enforce this rule because it is on the default consistent
. We should really look at adding a number of rules to the markdownlint
configuration to better enforce our preferred Markdown style.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mcdonnnj I believe it was automatically enforcing it when I ran precommit for the python-library-skeleton, but it doesn't do it in the skeleton-docker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zenine07 The default of consistent
will only flag if you are using different styles. Since you did not merge in the skeleton's README you are consistently using the ATX style (and not the ATX closed style we prefer).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…nd-wheel-with-pip Install/upgrade setuptools and wheel when upgrading pip
🗣 Description
This PR would reintegrate the cisagov/skeleton-docker skeleton into this repository.
This was done by adding the correct skeleton repository as a remote, pulling from its develop branch, and resolving any conflicts shown.
After skeleton was merged, fixed pre-commit issues that showed up.
💭 Motivation and Context
When this project was created, it was not started using the
skeleton
tool This prevents thelineage
GitHub Action from automatically generating PRs to ensure downstream repositories are kept up-to-date.🧪 Testing
Automated tests pass.
🚥 Types of Changes
✅ Checklist