forked from Kong/kong-vagrant
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adding Dependabot to your Repository - Security Team #4
Open
ecobee-dependabot-scanner
wants to merge
32
commits into
master
Choose a base branch
from
Dependabot-Scanner-2020-07-22
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SBP-4367: Hot module reload for plugins
SBP-4380: update startup of vagrant container
SBP-4433: update plugin config in sb-kong-vagrant
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated Dependabot Integration Scanner
Purpose
Hi team, our security bot has found that your repository is missing the dependabot integration.
The purpose of this bot is to help secure your application by limiting the vulnerabilities that you may be exposed to by virtue of insecure dependencies.
If you already have dependabot integrated in your repository, please see the last section.
If you aren't yet using dependabot, see below next steps:
What should I do to close this PR?
Check which package manager you use, if its not one from this list, please comment on this PR linking someone on the Security Team to verify and close the Pull Request
javascript
ruby:bundler
php:composer
python
go:modules
go:dep
java:maven
java:gradle
dotnet:nuget
rust:cargo
elixir:hex
docker
terraform
submodules
elm
See the following docs and make changes to the template config we have provided you:
https://dependabot.com/docs/config-file/
If you would like some examples, see the following repositories:
https://github.com/ecobee/security-theia-cloudtrail-slack/blob/master/.dependabot/config.yml
https://github.com/ecobee/smartbuildings/blob/develop/.dependabot/config.yml
https://github.com/ecobee/admin-portal/blob/main/.dependabot/config.yml
Merge this PR!
Add your repository to the Dependabot API so that it can begin tracking your dependencies using the configuration file you merged.
https://app.dependabot.com/accounts/ecobee
Make sure to perform this step! If you don't another PR will be created tomorrow
I already have Dependabot integrated in this repository, why am I getting this?
Our bot is perfect, it cannot yet detect if you are using Dependabot V2 (yet), so if you are please follow the below steps:
I confirm dependabot is already in our repository
a. The PR should be automatically closed
If the above steps did not work, please reach out to the security team so that we may help you close the PR correctly (so that it doesn't get recreated in the future)
Brought to you by the Security team.
If you have any questions don't hesitate to message us.