{"action":"created","issue":{"url":"https://api.github.com/repos/bundler/bundler/issues/3697","labels_url":"https://api.github.com/repos/bundler/bundler/issues/3697/labels{/name}","comments_url":"https://api.github.com/repos/bundler/bundler/issues/3697/comments","events_url":"https://api.github.com/repos/bundler/bundler/issues/3697/events","html_url":"https://github.com/bundler/bundler/issues/3697","id":83044315,"number":3697,"title":"Do not update BUNDLED WITH if no other changes to the lock happened","user":{"login":"jhass","id":141294,"avatar_url":"https://avatars.githubusercontent.com/u/141294?v=3","gravatar_id":"","url":"https://api.github.com/users/jhass","html_url":"https://github.com/jhass","followers_url":"https://api.github.com/users/jhass/followers","following_url":"https://api.github.com/users/jhass/following{/other_user}","gists_url":"https://api.github.com/users/jhass/gists{/gist_id}","starred_url":"https://api.github.com/users/jhass/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhass/subscriptions","organizations_url":"https://api.github.com/users/jhass/orgs","repos_url":"https://api.github.com/users/jhass/repos","events_url":"https://api.github.com/users/jhass/events{/privacy}","received_events_url":"https://api.github.com/users/jhass/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-05-31T09:01:02Z","updated_at":"2015-06-02T12:54:22Z","closed_at":"2015-05-31T16:54:50Z","body":"Running `bundle install` (e.g. as a dev on a project) and having a newer version of bundler, writes that newer version into the lock. This makes the lock dirty, leaving you with the option to 1) make a meaningless commit to bump the bundler version referenced in it or 2) constantly run `git checkout Gemfile.lock` as you switch branches, rebase and so on.\r\n\r\nIf there were no other changes to the lock, we know that the previous version of Bundler was not only working for the lock and the corresponding Gemfile, in fact we know that there's very likely not even the slightest difference in behaviour for it.\r\n\r\nI'm happy to look into a fix if you have some pointers, like where one could decide to not write the lock at all if it wasn't changed."},"comment":{"url":"https://api.github.com/repos/bundler/bundler/issues/comments/107943904","html_url":"https://github.com/bundler/bundler/issues/3697#issuecomment-107943904","issue_url":"https://api.github.com/repos/bundler/bundler/issues/3697","id":107943904,"user":{"login":"jhass","id":141294,"avatar_url":"https://avatars.githubusercontent.com/u/141294?v=3","gravatar_id":"","url":"https://api.github.com/users/jhass","html_url":"https://github.com/jhass","followers_url":"https://api.github.com/users/jhass/followers","following_url":"https://api.github.com/users/jhass/following{/other_user}","gists_url":"https://api.github.com/users/jhass/gists{/gist_id}","starred_url":"https://api.github.com/users/jhass/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhass/subscriptions","organizations_url":"https://api.github.com/users/jhass/orgs","repos_url":"https://api.github.com/users/jhass/repos","events_url":"https://api.github.com/users/jhass/events{/privacy}","received_events_url":"https://api.github.com/users/jhass/received_events","type":"User","site_admin":false},"created_at":"2015-06-02T12:54:21Z","updated_at":"2015-06-02T12:54:21Z","body":"@chemica are you using spring or guard?"}}