latest 20 messages by axilla
+
[2017-01-18T14:52:59Z]
axilla
was our issue.. we got it resolved.
+
[2017-01-18T14:52:24Z]
axilla
not that one
+
[2017-01-18T14:52:17Z]
axilla
the restrict who can push check
+
[2017-01-18T14:51:43Z]
axilla
weird.. we've been using it with the same settings for months and didnt have any problems until today
+
[2017-01-18T14:40:16Z]
axilla
a notice would have been nice
+
[2017-01-18T14:40:07Z]
axilla
nevermind, we found some new settings that look to have been changed regarding branch protection
+
[2017-01-18T14:36:28Z]
axilla
we have branch protection on, and if we turn it off he can merge
+
[2017-01-18T14:35:35Z]
axilla
any ideas?
+
[2017-01-18T14:35:28Z]
axilla
and he's a team member/collaborator
+
[2017-01-18T14:35:03Z]
axilla
it says he needs to be added as a collaborator to merge
+
[2017-01-18T14:34:37Z]
axilla
but he can't push or merge
+
[2017-01-18T14:34:29Z]
axilla
he has all the correct access permissions
+
[2017-01-18T14:34:23Z]
axilla
morning all, i have an issue without github account.. we've added a new team member
+
[2016-12-14T18:23:35Z]
axilla
seems like a poor choice
+
[2016-12-14T18:23:08Z]
axilla
instead of doing a merge from master?
+
[2016-12-14T18:23:04Z]
axilla
shouldn't it rebase onto it
+
[2016-12-14T18:22:59Z]
axilla
is there a good reason for the new merge conflict resolution to show up as a merge from the parent branch?
+
[2016-08-31T20:43:55Z]
axilla
using the same key
+
[2016-08-31T20:43:52Z]
axilla
i think it might have been created by github for mac? but i've had it installed for a long time
+
[2016-08-31T20:42:45Z]
axilla
changed my password.. any way this was a github error or should I be worried?