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 GitHub Action for updating license file for dependabot branches #1517
Conversation
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.
very cool time saver, better than my idea 😄
Kudos, SonarCloud Quality Gate passed! |
Codecov Report
@@ Coverage Diff @@
## develop #1517 +/- ##
========================================
Coverage 43.88% 43.88%
========================================
Files 312 312
Lines 9380 9380
Branches 2244 2244
========================================
Hits 4116 4116
Misses 3433 3433
Partials 1831 1831 Continue to review full report at Codecov.
|
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.
Neat, I did not know you could do 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.
Nice one!
Description
This PR adds a GitHub action that is triggered on a push event for branches that begin with
dependabot/
, updates the license file, and pushes the changes if there are any.From dependabot docs:
If you happen to create a branch that starts with
dependabot/
then this action will run, but it's probably unlikely to happen since we use hubflow.A git name and email has to be set in order to commit something. I used option 2 in this comment to display that the user who performed the commit is the GitHub Action bot.
An example of this GitHub action running is in this draft PR: #1516.
Issue
SEAB-4223
Please make sure that you've checked the following before submitting your pull request. Thanks!
npm run build
markdown-wrapper
component, which does extra sanitizationnpm audit
and ensure you are not introducing new vulnerabilities