kevin.rushforth at oracle.com
Thu Mar 4 17:18:15 UTC 2021
This can be configured on a per-project basis. For example, the jfx
project is not setup to auto-close old PRs. If the jdk project so
chooses, it can easily be disabled for that project as well. Perhaps you
can raise this issue on jdk-dev?
As for the other point, I can't think of a good reason that the PR
author should not be able to reopen their own PR. That sounds like a
problem with the way the jdk repo, or perhaps the openjdk group, on
GitHub is configured.
On 3/4/2021 9:05 AM, Thomas Stüfe wrote:
> I would prefer that too.
> On Thu, Mar 4, 2021 at 2:02 PM Mario Torre <neugens at redhat.com> wrote:
>> More generally, we should probably disable those automatic stuff-closing
>> bots, it doesn't make much sense to me.
>> On Thu, Mar 4, 2021 at 12:32 PM Aleksey Shipilev <shade at redhat.com> wrote:
>>> Look at this issue:
>>> It was closed by bot due to timeout:
>>> "@shipilev This pull request has been inactive for more than 8 weeks and
>> will now be automatically
>>> closed. If you would like to continue working on this pull request in
>> the future, feel free to
>>> reopen it!"
>>> Cool, but there is no way for me to reopen the PR.
>>> It must be because the bot closed the PR, and I don't have enough
>> privileges to reopen?
>>> What users like me are expected to do here?
>> Mario Torre
>> Manager, Software Engineering
>> Red Hat GmbH <https://www.redhat.com>
>> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898
More information about the skara-dev