-
Notifications
You must be signed in to change notification settings - Fork 13
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
greenkeeper/initial #5
base: master
Are you sure you want to change the base?
Conversation
Let’s get started with automated dependency management for maven-code-quality-pom 💪
This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point for keeping up with new releases. Greenkeeper will look out for further dependency updates and make sure to handle them in isolation and in real-time, but only after you merge this pull request. Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request. 💥 Tests on this branch are failing. Here’s how to proceed.To solve the issue, first find out which of the dependency’s updates is causing the problem. Then fix your code to accomodate the changes in the updated dependency. next-update is a really handy tool to help you with this. Then push your changes to this branch and merge it. 🏷 How to check the status of this repositoryGreenkeeper adds a badge to your README which indicates the status of this repository. 🙈 How to ignore certain dependenciesYou may have good reasons for not wanting to update to a certain dependency right now. In this case, you can change the dependency’s version string in the To make sure Greenkeeper doesn’t nag you again on the next update, add a // package.json
{
…
"greenkeeper": {
"ignore": [
"package-names",
"you-want-me-to-ignore"
]
}
} 👩💻 How to update this pull request # Change into your repository’s directory
git fetch
git checkout greenkeeper/initial
npm install-test
# Adapt your code until everything works again
git commit -m 'chore: adapt code to updated dependencies'
git push origin greenkeeper/initial ✨ How do dependency updates work with Greenkeeper?After you merge this pull request, Greenkeeper will create a new branch whenever a dependency is updated, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date. - "underscore": "^1.6.0"
+ "underscore": "^1.7.0" The above example shows an in-range update. However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately. This way, you’ll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, you’ll be the first to know. - "lodash": "^3.0.0"
+ "lodash": "^4.0.0" In this example, the new version This means that you no longer need to check for new versions manually – Greenkeeper will keep you up to date automatically. These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away To get a better idea of which ranges apply to which releases, check out the extremely useful semver calculator provided by npm. FAQ and helpThere is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. Good luck with your project and see you soon ✨ Your Greenkeeper bot 🌴 |
1 similar comment
Alt text is now "MIT License" #1, #$
Modified estimate to account for greenkeeper's lockfile. |
1 similar comment
1 similar comment
Hey there 👋, we noticed that this PR isn’t merged yet. Just to let you know: if you don't merge this PR, Greenkeeper will not be enabled on this repo, and you won't receive updates for your dependencies. If don't want to enable Greenkeeper here, just close or ignore this PR, we won't nag you again. ✌️ Have a great day! 🌴 |
1 similar comment
* chore(package): update dependencies * docs(readme): add Greenkeeper badge * docs(readme): add greenkeeper badge Closes #1 * docs(license): edit license badge's alt text Alt text is now "MIT License" #1, #$ * docs(readme): init greenkeeper Clean up README, too. #1,#5 * ci(blackduck-copilot): enable CoPilot SaaS * ci(dependency-ci): add config for removed libs * fix(pom): Running "mvn site" results in error with message "Could not connect to Central search" Applied the fix described here: jeremylong/DependencyCheck#978 #8 * build(mvnw): add /.mvn/ directory #10 * docs(styleguide): add markdown styleguide Format all Java source #10,#11
* chore(license): might need to evaluate a LGLPL license. * chore(package): update dependencies * docs(readme): add Greenkeeper badge * docs(readme): add greenkeeper badge Closes #1 * docs(license): edit license badge's alt text Alt text is now "MIT License" #1, #$ * docs(readme): init greenkeeper Clean up README, too. #1,#5 * ci(blackduck-copilot): enable CoPilot SaaS * ci(dependency-ci): add config for removed libs * fix(pom): Running "mvn site" results in error with message "Could not connect to Central search" Applied the fix described here: jeremylong/DependencyCheck#978 #8 * build(mvnw): add /.mvn/ directory #10 * docs(styleguide): add markdown styleguide Format all Java source #10,#11 * docs(mvn-site): update with latest info * ci(quality): add tooling 1. google-java-format: format all source code 2. javac-with-errorprone: static code analyzer
Description of change
Allow Greenkeeper to manage JavaScript dependency drift with automated updates and PRs.
Associated issue(s)
Closes #1
PR check-list
1. Acceptance criteria
2. Test coverage
3. Code standards compliance
3.1. JavaScript
ESLint
passes.3.2. Java
Checkstyle
passesPMD
passesFindbugs
passes4. Code quality
Complexity
Duplications
Issues
Maintainability
Reliability
Security