GitHub is a read-only mirror, but ihasmail.org's "Get the source" button
goes there, so reports keep landing on GitHub (GitHub issues 418 and 419 were filed there
and had to be carried over). GitHub's New issue page now shows links to
the Gitea issue tracker, the community forum and SECURITY.md instead of a
blank form.
Gitea falls back to .github/ISSUE_TEMPLATE/config.yml when it has none of
its own, so .gitea/ISSUE_TEMPLATE/config.yml keeps blank issues on here.
Gitea links to git.coffeylabs.org/coffey-labs/ihasmail/issues are unaffected: Gitea's issue form is unchanged.
After merge, the mirror pushes this to GitHub; check github.com/Coffey-Labs/ihasmail/issues/new/choose shows the three links.
GitHub is a read-only mirror, but ihasmail.org's "Get the source" button
goes there, so reports keep landing on GitHub (GitHub issues 418 and 419 were filed there
and had to be carried over). GitHub's New issue page now shows links to
the Gitea issue tracker, the community forum and SECURITY.md instead of a
blank form.
Gitea falls back to .github/ISSUE_TEMPLATE/config.yml when it has none of
its own, so .gitea/ISSUE_TEMPLATE/config.yml keeps blank issues on here.
Gitea links to git.coffeylabs.org/coffey-labs/ihasmail/issues are unaffected: Gitea's issue form is unchanged.
After merge, the mirror pushes this to GitHub; check github.com/Coffey-Labs/ihasmail/issues/new/choose shows the three links.
GitHub is a read-only mirror, but ihasmail.org's "Get the source" button
goes there, so reports keep landing on GitHub (GitHub issues 418 and 419 were filed there
and had to be carried over). GitHub's New issue page now shows links to
the Gitea issue tracker, the community forum and SECURITY.md instead of a
blank form.
Gitea falls back to .github/ISSUE_TEMPLATE/config.yml when it has none of
its own, so .gitea/ISSUE_TEMPLATE/config.yml keeps blank issues on here.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
GitHub is a read-only mirror, but ihasmail.org's "Get the source" button
goes there, so reports keep landing on GitHub (GitHub issues 418 and 419 were filed there
and had to be carried over). GitHub's New issue page now shows links to
the Gitea issue tracker, the community forum and SECURITY.md instead of a
blank form.
Gitea falls back to .github/ISSUE_TEMPLATE/config.yml when it has none of
its own, so .gitea/ISSUE_TEMPLATE/config.yml keeps blank issues on here.
Gitea links to git.coffeylabs.org/coffey-labs/ihasmail/issues are unaffected: Gitea's issue form is unchanged.
After merge, the mirror pushes this to GitHub; check github.com/Coffey-Labs/ihasmail/issues/new/choose shows the three links.