Would archiving the repository work for this? [1]
-- Kevin
[1]
https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository
On 3/30/2021 11:16 AM, John Neffenger wrote:
On 3/28/21 5:24 AM, Johan Vos wrote:
I'm still in favor of closing it thoug
On 3/28/21 5:24 AM, Johan Vos wrote:
I'm still in favor of closing it though.
It would be nice if there were a way in GitHub to close the repository
to new issues but keep the old ones public and editable. For example,
I'm still getting good information on the old closed issues, even as
rece
Can you make it private? This way we could still see if there are relevant
issues there like those that halted during the transition.
On Sun, Mar 28, 2021 at 3:24 PM Johan Vos wrote:
> I'm creating a separate thread for this, as it might get lost in other
> threads.
> We see that issues are stil
I'm creating a separate thread for this, as it might get lost in other
threads.
We see that issues are still created in the old
github.com/javafxports/openjdk-jfx project. The README of that project
clearly mentions that repository is obsolete, but the issue tracker is
still open.
It is not hard to
