Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

needs manual testing #74

Open
bilalcaliskan opened this issue Aug 15, 2022 · 4 comments
Open

needs manual testing #74

bilalcaliskan opened this issue Aug 15, 2022 · 4 comments

Comments

@bilalcaliskan
Copy link
Owner

No description provided.

@Francishamilton96
Copy link

Yes

@github-actions
Copy link
Contributor

This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2022
@bilalcaliskan bilalcaliskan reopened this Dec 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jun 4, 2023

This bot triages issues and PRs according to the following rules: - After 180d of inactivity, lifecycle/stale is applied. - After 90d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 180d days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

Copy link
Contributor

github-actions bot commented Dec 3, 2023

This bot triages issues and PRs according to the following rules: - After 180d of inactivity, lifecycle/stale is applied. - After 90d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 180d days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants