Skip to content

Our Policy on Issues #1305

Closed
Closed
@LeoNatan

Description

@LeoNatan

General Policy

In this project, our preferred focus with respect to the issue tracker is mainly on 2 things:

  1. Bug reports
  2. Feature/enhancement requests

Nevertheless, we do allow for requests for help to be posted on any general matter, but with some caveats - please read below.

Before submitting a new issue, be sure to select the best option in the new-issue form.

🛟 Using issues for getting help

The Detox project is maintained by a core-team of domain experts, that is powerful, yet minimal in size. While we care a lot about the community and our users' success, our first commitment is to push the project forward by focusing on innovation and new, large-scale features.

For getting help with specific things such as integrating Detox in your project or running it on a specific CI SaaS, it would make a better idea to first approach our Discord community or posting Stack-Overflow, as suggested by the issue submission form.

For removing personal blockers or for contributing back to the community by improving Detox - namely, by introducing new API's or specific bug fixes, please consider onboarding the project contribution and submitting a fully-fledged pull request. Improvement suggestions are more likely to fall between the cracks.

Before submitting a pull request, please voice your suggested idea as an issue, to allow for a discussion with the maintainers.

⚠️ Detox is a community project, and everyone is a potential maintainer. Making an impact is under everyone's responsibility. 🙏🏻

🤖 Automations

We do our best to go over issues and pull requests and tag them as accurately as possible, and through that - provide a solution as fast as possible. However, we are a small team and have limited capacity; We even often have other projects we are working on. Therefore, we utilize some automations rules to help us run things more smoothly, nonetheless:

  1. Support: When it comes to general questions and requests for help, we initially review the issue, but may often find that posting them on Stack Overflow - the ultimate Q&A platform, would be more suitable. Detox even has its own designated detox label. When that happens, we mark issue with a special label, and a bot provides all the necessary info through a comment.

  2. Stale: Issues and pull requests that become inactive for too long get marked as stale. This is a wake up call for both us as maintainers and the issue reporter that attention is required. If applicable, feel free to post new comments on the issue in order to "unstale" it. In any case, anything that's stale for too long gets closed (but not locked!).

  3. No Response: In order to be able to help - especially with bugs, we require some information from your side. Sometimes that can be overwhelming, but the fact of the matter is that in this complex project, too little info makes it extremely difficult to help out. In those cases, we mark issues with a special label, requesting you to fill in the missing pieces. As we have no other choice, this starts a countdown for the issue to be closed, unless more info is provided.

  4. Lock: Quite rarely, after long periods of inactivity, closed issues and pull requests will also be locked.

Bots that run these behind the scenes: Support, No Response, Stale, Lock

Note that no system is perfect, and sometimes things fall between the cracks. Feel free to ping us when necessary.

Thank you for using Detox!

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions