nbot.meta

Issues/PRs archive for MTRNord/nBot
git clone git://archive.git.mtrnord.blog/MTRNord/nbot.meta.git
Log | Files | Refs

21.md (4001B)

      1 # PR #21 Update dependencies to enable Greenkeeper 🌴
      2 
      3 - **Status:** merged
      4 - **Author:** @greenkeeper[bot]
      5 - **Created:** 2017-02-11T12:08:06Z
      6 - **Branch:** greenkeeper/initial → master
      7 - **Merged:** 2017-02-11T12:34:08Z
      8 - **Labels:** greenkeeper
      9 - **Diff:** [21.diff](./21.diff)
     10 
     11 ---
     12 
     13 Let’s get started with automated dependency management for nBot :muscle:
     14 
     15 This pull request **updates all your dependencies to their latest version**. Having them all up to date really is the best starting point. I will look out for further dependency updates and make sure to handle them in isolation and in real-time, **as soon as you merge this pull request**.
     16 
     17 **I won’t start sending you further updates, unless you have merged this very pull request**.
     18 
     19 ---
     20 
     21 
     22 
     23 
     24 
     25 
     26 <details>
     27 <summary>🏷 How to check the status of this repository</summary>
     28 There is a badge added to your README, indicating the status of this repository.
     29 
     30 This is how your badge looks like :point_right:  ![Greenkeeper badge](https://badges.greenkeeper.io/MTRNord/nBot.svg)
     31 </details>
     32 
     33 
     34 
     35 <details>
     36 <summary>👩‍💻 How to update this pull request</summary>
     37 
     38 ```bash
     39 # change into your repository’s directory
     40 git fetch
     41 git checkout greenkeeper/initial
     42 npm install-test
     43 # adapt your code, so it’s working again
     44 git commit -m 'chore: adapt code to updated dependencies'
     45 git push origin greenkeeper/initial
     46 ```
     47 </details>
     48 
     49 <details>
     50 <summary>🙈 How to ignore certain dependencies</summary>
     51 
     52 In case you can not, or do not want to update a certain dependency right now, you can of course just [change the `package.json` file back to your liking](https://github.com/MTRNord/nBot/edit/greenkeeper/initial/package.json).
     53 
     54 Add a `greenkeeper.ignore` field to your `package.json`, containing a list of dependencies you don’t want to update right now.
     55 
     56 ```js
     57 // package.json
     58 {
     59   …
     60   "greenkeeper": {
     61     "ignore": [
     62       "package-names",
     63       "you-want-me-to-ignore"
     64     ]
     65   }
     66 }
     67 ```
     68 </details>
     69 
     70 <details>
     71 <summary>✨ How the updates will look like</summary>
     72 
     73 As soon as you merge this pull request **I’ll create a branch for every dependency update**, with the new version applied. The branch creation should trigger your testing services to check the new version. Using the results of these tests I’ll try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.
     74 
     75 ```diff
     76 -  "underscore": "^1.6.0"
     77 +  "underscore": "^1.7.0"
     78 ```
     79 
     80 In the above example you can see an in-range update. `1.7.0` is included in the old `^1.6.0` range, because of the [caret `^` character ](https://docs.npmjs.com/misc/semver#ranges).
     81 When the test services report success I’ll delete the branch again, because no action needs to be taken – everything is fine.
     82 When there is a failure however, I’ll create an issue so you know about the problem immediately.
     83 
     84 This way every single version update of your dependencies will either continue to work with your project, or you’ll get to know of potential problems immediately.
     85 
     86 ```diff
     87 -  "lodash": "^3.0.0"
     88 +  "lodash": "^4.0.0"
     89 ```
     90 
     91 In this example the new version `4.0.0` is not included in the old `^3.0.0` range.
     92 For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.
     93 
     94 Now **you no longer need to check for exciting new versions by hand** – I’ll just let you know automatically.
     95 And the pull request will not only serve as a reminder to update. In case it passes your decent test suite that’s a strong reason to merge right away :shipit:
     96 </details>
     97 
     98 <details>
     99 <summary>💁‍♂️ Not sure how things are going to work exactly?</summary>
    100 
    101 There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
    102 </details>
    103 
    104 
    105 ---
    106 
    107 
    108 Good luck with your project and see you soon :sparkles:
    109 
    110 Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
    111 
    112