latest 20 messages by BtbN
+
[2020-07-11T22:58:14Z]
BtbN
it's a 3rd party after all
+
[2020-07-11T22:58:06Z]
BtbN
That's up to travis, not Github
+
[2020-07-09T22:33:47Z]
BtbN
Would never have heard of that before
+
[2020-07-07T18:40:48Z]
BtbN
Then seeing that list would be quite a security messup on Githubs end.
+
[2020-07-07T18:39:20Z]
BtbN
Is it your repo?
+
[2020-07-07T18:32:09Z]
BtbN
Look at the settings of it and its org
+
[2020-07-03T01:04:23Z]
BtbN
If someone has push access, they can push whatever they feel like, and if not protected against force-push away all commits.
+
[2020-06-26T18:01:39Z]
BtbN
If someone closes it manually, that's hardly a bug
+
[2020-06-26T18:01:31Z]
BtbN
???
+
[2020-06-26T18:00:34Z]
BtbN
Creating a pull request is always allowed, it just cannot be merged.
+
[2020-06-26T17:50:25Z]
BtbN
It cannot magically solve the conflicts
+
[2020-06-26T17:50:19Z]
BtbN
No, it's exactly what happens when there are conflicts
+
[2020-06-26T17:44:29Z]
BtbN
Which is exactly what's written there as well.
+
[2020-06-26T17:44:19Z]
BtbN
Again: If there are no conflicts, the source branch behind behind the target does not matter.
+
[2020-06-26T17:43:43Z]
BtbN
I am well aware of how Pull requests work
+
[2020-06-26T17:42:55Z]
BtbN
Sorry, but I cannot follow what you're trying to say at all.
+
[2020-06-26T17:40:47Z]
BtbN
Provided there are no conflicts, like I said
+
[2020-06-26T17:40:38Z]
BtbN
When you hit merge on a PR, it certainly will apply the new commits on top.
+
[2020-06-26T17:40:13Z]
BtbN
what?
+
[2020-06-26T17:39:59Z]
BtbN
A pull request is effectively saying "merge all commits from this branch that are not in $targetBranch into it"