NeoNeko/Community-Issues
Watch
1
0
Fork
You've already forked Community-Issues
 0
Code Issues 1 Pull requests Activity

Read First before reporting an issues #1

New issue
Open
opened 2026-08-15 23:14:58 +00:00 by Yusarina · 0 comments
Yusarina commented 2026-08-15 23:14:58 +00:00
Owner
Copy link

Community Issues

The place to report problems with the things NeoNeko runs: this git instance,
the website, and the status page.

There is no code in this repository. It exists so there is somewhere public to
report a broken thing, and so that when someone else hits the same problem they
can find the answer instead of asking again.

Report here
git.neoneko.org Bugs, broken pages, slow loading, Actions and runner problems, API oddities, anything that behaves wrong
neoneko.org Broken links, wrong information, display problems
status.neoneko.org The status page itself misbehaving

Feature requests and "would it be possible to" questions about the instance are
welcome too.

Report somewhere else

Some things do not belong in a public issue tracker, either because they are
about a specific project or because they should not be public at all.

What Where
Cats Blender Plugin bugs Cats issues
NeoStatus bugs NeoStatus issues
Your account, login, email, deletion support@neoneko.org
Harassment, abuse, someone's behaviour abuse@neoneko.org
Copyright, legal notices, data protection legal@neoneko.org
A security vulnerability support@neoneko.org, not a public issue

Never open a public issue to report harassment or a security hole. For
harassment that means naming someone publicly before anyone has looked at it,
and reports to abuse@ stay private. For a vulnerability it means publishing the
hole before it is fixed. Both go to email.

Before you open one

  • Have a look at status.neoneko.org. If something
    is already known to be down, it will say so.
  • Search the existing issues, including closed ones.
  • If you can, try it in another browser or a private window. It saves a round
    trip when the answer turns out to be a cached page or an extension.

What to put in it

The more of this you include, the faster it gets sorted:

  • What you did, what happened, and what you expected instead
  • The URL it happened on
  • Roughly when, and whether it happens every time
  • Your browser and operating system, if it looks like a display problem
  • A screenshot, if it is something you can see
  • For Actions problems: which repository, a link to the run, and what the job
    is meant to do

This repository is public

Anyone can read it, and search engines index it. Do not paste:

  • access tokens, passwords or SSH keys
  • the contents of a private repository
  • someone else's email address or personal details

If you accidentally post a token, revoke it rather than only deleting the
comment. Assume anything published here has already been copied.

What to expect

NeoNeko is one person. There is no support rota and no response time promise.
Issues are read, serious things get looked at first, and quiet does not mean
ignored.

If something is completely broken and affecting everyone, it will usually show
on the status page before anyone has time to write an issue.

Policies

The Guidelines apply here as much as anywhere else on the instance. Short
version: disagreement and bluntness are fine, aiming at people is not.

# Community Issues The place to report problems with the things NeoNeko runs: this git instance, the website, and the status page. There is no code in this repository. It exists so there is somewhere public to report a broken thing, and so that when someone else hits the same problem they can find the answer instead of asking again. ## Report here | | | |---|---| | **git.neoneko.org** | Bugs, broken pages, slow loading, Actions and runner problems, API oddities, anything that behaves wrong | | **neoneko.org** | Broken links, wrong information, display problems | | **status.neoneko.org** | The status page itself misbehaving | Feature requests and "would it be possible to" questions about the instance are welcome too. ## Report somewhere else Some things do not belong in a public issue tracker, either because they are about a specific project or because they should not be public at all. | What | Where | |---|---| | Cats Blender Plugin bugs | [Cats issues](https://git.neoneko.org/NeoNeko/Cats-Blender-Plugin/issues) | | NeoStatus bugs | [NeoStatus issues](https://git.neoneko.org/NeoNeko/NeoStatus/issues) | | Your account, login, email, deletion | support@neoneko.org | | Harassment, abuse, someone's behaviour | abuse@neoneko.org | | Copyright, legal notices, data protection | legal@neoneko.org | | A security vulnerability | support@neoneko.org, **not** a public issue | **Never open a public issue to report harassment or a security hole.** For harassment that means naming someone publicly before anyone has looked at it, and reports to abuse@ stay private. For a vulnerability it means publishing the hole before it is fixed. Both go to email. ## Before you open one - Have a look at [status.neoneko.org](https://status.neoneko.org). If something is already known to be down, it will say so. - Search the existing issues, including closed ones. - If you can, try it in another browser or a private window. It saves a round trip when the answer turns out to be a cached page or an extension. ## What to put in it The more of this you include, the faster it gets sorted: - What you did, what happened, and what you expected instead - The URL it happened on - Roughly when, and whether it happens every time - Your browser and operating system, if it looks like a display problem - A screenshot, if it is something you can see - For Actions problems: which repository, a link to the run, and what the job is meant to do ## This repository is public Anyone can read it, and search engines index it. Do not paste: - access tokens, passwords or SSH keys - the contents of a private repository - someone else's email address or personal details If you accidentally post a token, revoke it rather than only deleting the comment. Assume anything published here has already been copied. ## What to expect NeoNeko is one person. There is no support rota and no response time promise. Issues are read, serious things get looked at first, and quiet does not mean ignored. If something is completely broken and affecting everyone, it will usually show on the status page before anyone has time to write an issue. ## Policies - [Terms of Service](https://neoneko.org/terms.html) - [Privacy Policy](https://neoneko.org/privacy.html) - [Community Guidelines](https://neoneko.org/guidelines.html) The Guidelines apply here as much as anywhere else on the instance. Short version: disagreement and bluntness are fine, aiming at people is not.
Yusarina locked and limited conversation to collaborators 2026-08-15 23:15:11 +00:00
This discussion has been locked. Commenting is limited to contributors.
main
Branches Tags
Clear current reference
main
Clear current reference
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
NeoNeko/Community-Issues#1
No description provided.