{"issue":{"user":{"id":867780,"login":"johnhaley81","url":"https://api.github.com/users/johnhaley81","gravatar_id":"cf1946e98f7ab6d27a3858395c7bea03","avatar_url":"https://secure.gravatar.com/avatar/cf1946e98f7ab6d27a3858395c7bea03?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"milestone":null,"title":"Bug with distinct when rebasing.","created_at":"2011-12-20T18:18:35Z","labels":[],"state":"closed","updated_at":"2011-12-20T19:23:17Z","id":2616107,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/github/github-services/issues/205","closed_at":"2011-12-20T19:23:17Z","body":"So in the payload sent from github-services there's a 'distinct' field that is labelled \"new to the repository\". But I found a way to get that flag to be true even if the commit isn't new to the repo.\r\n\r\nSay you have a commit on branch in github labelled 'a' and that is based off of master. We'll say that 'a' is 2 commits behind master and is 1 commit infront and all of these changes already exist in github. If you rebase 'a' on master, then fast-forward master with that new commit and then push that change to github, the 'distinct' flag is set to true even though that commit is already in 'a' on github.\r\n\r\nIs this the expected behavior?","number":205,"url":"https://api.github.com/repos/github/github-services/issues/205","comments":4,"assignee":null},"comment":{"user":{"id":2567,"login":"tmm1","url":"https://api.github.com/users/tmm1","gravatar_id":"d47656e20ff5e42f125fc5ea0fd636c6","avatar_url":"https://secure.gravatar.com/avatar/d47656e20ff5e42f125fc5ea0fd636c6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-20T19:23:17Z","updated_at":"2011-12-20T19:23:17Z","id":3223781,"body":"Closing. As stated, this is expected since \"a\" is no longer really \"a\" when you rebase it.","url":"https://api.github.com/repos/github/github-services/issues/comments/3223781"},"action":"created"}