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

upstream reference closed: github.com/GoogleContainerTools/distroless/issues/1342 #1413

Closed
1 task
github-actions bot opened this issue Aug 31, 2023 · 1 comment
Closed
1 task
Labels
good first issue A good issue to tackle when being a novice to the project. help wanted We are looking for help on this one. stale Feedback from one or more authors is required to proceed. upstream Issue is caused by an upstream dependency.

Comments

@github-actions
Copy link

The upstream issues got closed. It is referenced in:

This issue was created by the ORY Closed Reference Notifier GitHub action.

@github-actions github-actions bot added good first issue A good issue to tackle when being a novice to the project. help wanted We are looking for help on this one. upstream Issue is caused by an upstream dependency. labels Aug 31, 2023
Copy link
Author

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
  • leave a comment and describe in detail why this issue is critical for your use case;
  • open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

@github-actions github-actions bot added the stale Feedback from one or more authors is required to proceed. label Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue A good issue to tackle when being a novice to the project. help wanted We are looking for help on this one. stale Feedback from one or more authors is required to proceed. upstream Issue is caused by an upstream dependency.
Projects
None yet
Development

No branches or pull requests

0 participants