-
Notifications
You must be signed in to change notification settings - Fork 48
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
add git secrets ci ros1 #95
Conversation
Blocked by aws-robotics/aws-robomaker-github-actions#17. Before merging, requires version bump (to 2.3.4) for all aws-robomaker-gh-actions after is merged. |
The comments in #94 also apply here. |
.github/workflows/ros1.yml
Outdated
@@ -41,17 +41,19 @@ jobs: | |||
run: | | |||
# TODO(ros-tooling/setup-ros-docker#7): calling chown is necessary for now | |||
sudo chown -R rosbuild:rosbuild "$HOME" . | |||
- name: Scan using git-secrets | |||
uses: aws-robotics/aws-robomaker-github-actions/git-secrets-scan-action@2.4.0 |
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.
You had a concern that doing --scan-history
would take a long time, right?
Anyway, I think we should move the scan to a separate workflow YAML file, so that the scanning can take place in parallel with building and bundling.
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.
Yes I did.. but I tested --scan-history on some public repos with signicantly larger commit history and the time doesn't seem to exceed more than a minute at the most. I feel that should be considerably lesser than what build and bundle takes.
Bump to 2.4.1
Bump to 2.4.1
Issue #, if available:
Description of changes:
Adding git secrets scan action to ROS1 workflows
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.