# activitypub-testing/issues

This directory is the issue tracker for `activitypub-testing`.

If you are having an issue using activitypub-testing, or you have an issue with the current set of functionality and would like it to be different, you are welcome to write a description of your issue as a file in this directory and commit it using [git](https://en.wikipedia.org/wiki/Git).

## Where to make Pull Requests

If you'd like your issue to be merged into the git repository of the activitypub-testing repository used by the creators of activitypub-testing, e.g. if you would like to bring it to their attention or request help in resolving your issue, make a pull request.

The best place to send a pull request to the activitypub-testing community is via the [codeberg.org/socialweb.coop/activitypub-testing][activitypub-testing-codeberg] repository.

[Click this link to add a new issue](https://codeberg.org/socialweb.coop/activitypub-testing/_new/main/issues) using the codeberg.org Web UI. [Markdown](https://en.wikipedia.org/wiki/Markdown) is a good syntax to use to describe your issue.

## Bugs

If you're filing a bug, try to include the following:

* what you did that led to the bug
* how the maintainers can try to reproduce the bug (e.g. sample inputs or invocations)
* what you expected to happen
* what actually happened
* details of your environment, e.g. Operating System, Browser, etc.

Why?

1. To fix the bug, and espeically to verify that it has been fixed after a change, the maintainers will probably need your help reproducing the bug or at least approximating it.
2. Discussing the gap between expected behavior and actual behavior can help get to the core of your issue as fast as possible and help the maintainers to both set realistic expectations and also improve the tool in the future to meet the expectations you already had.

## Why are you tracking issues in files and not a web based issue tracker?

1. to avoid reliance on any one issue tracking platform. git is peer to peer.
2. if you have the code, you have the issues, even if you're not connected to the internet for a bit
3. so issue details and lifecycle info can be updated in the same commit as the code change that resolves the issue

[activitypub-testing-codeberg]: https://codeberg.org/socialweb.coop/activitypub-testing