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

Docs enhancements #1578

Open
4 of 18 tasks
tnozicka opened this issue Nov 16, 2023 · 2 comments · May be fixed by #2188
Open
4 of 18 tasks

Docs enhancements #1578

tnozicka opened this issue Nov 16, 2023 · 2 comments · May be fixed by #2188
Assignees
Labels
kind/epic Categorizes issue as an epic. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tnozicka
Copy link
Member

tnozicka commented Nov 16, 2023

Tasks

  1. kind/documentation priority/important-soon
    tnozicka
  2. kind/documentation priority/important-soon
    tnozicka
  3. kind/documentation priority/important-soon
    tnozicka
  4. kind/documentation priority/important-soon
    tnozicka
  5. kind/documentation priority/important-longterm triage/accepted
    tnozicka
  6. kind/documentation priority/awaiting-more-evidence triage/accepted
  7. kind/documentation priority/important-longterm triage/accepted
  8. priority/backlog triage/accepted
    tnozicka
  9. kind/documentation priority/important-longterm
  10. kind/documentation priority/important-longterm triage/accepted
    rzetelskik tnozicka
  11. kind/documentation priority/important-longterm triage/accepted
  12. kind/documentation priority/important-longterm triage/accepted
@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/epic Categorizes issue as an epic. labels Nov 16, 2023
@tnozicka tnozicka self-assigned this Nov 16, 2023
Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2024
@tnozicka
Copy link
Member Author

tnozicka commented Jul 8, 2024

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 8, 2024
@tnozicka tnozicka linked a pull request Nov 15, 2024 that will close this issue
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Categorizes issue as an epic. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant