+ [2016-07-25T17:02:13Z] guardian hmm maybe not if I "squash & merge" that PR containing a single commit though
+ [2016-07-25T17:06:58Z] Zarthus i've not yet used it, but I do believe github offers that option
+ [2016-07-25T18:23:19Z] anew actually i did commit this file already
+ [2016-07-25T23:15:13Z] leehambley does anyone know what *kind* of API token is used by services such as Travis-CI? I'm trying to see in the documentation what it takes to list a service similar to Travis and what *kind* of token that is that Travis have posted to my Github account when I connected it ?
+ [2016-07-25T23:15:52Z] leehambley is it some kind of special-cased personal access token, or a general purpose OAuth token, and how is it that they have custom UI for that ?

message no. 144375

Posted by SlizardWizard in #github at 2016-07-25T04:43:50Z

I understand in the future i shouldn't commit to master when working on broken stuff but i still need to fix this issue now
+ [2016-07-26T00:46:03Z] kyan Hi! I've got a fork of a repository with some changes in it, and I want to make a new branch that is a clean copy of the original repository's master branch, so I can make changes and then make a pull request without it containing a lot of extra commits. How do I do that? Thanks! :)
+ [2016-07-26T01:39:32Z] jeffreylevesque i have questions regarding workflow: if i have one person working on milestone1, and another person working on milestone2, how should they be merging their issues, into master?
+ [2016-07-26T02:17:29Z] waveclaw do you use different feature branches or milestone branches for your milestones?
+ [2016-07-26T02:18:27Z] waveclaw if multiple people are merging into master you have to have the discipline to do frequent rebases or merge conflicts can start slowing down work and muddying the history.
+ [2016-07-26T02:49:27Z] kyan (I kinda figured out my question by making new branch from specific reviison. Thanks! :)