upstream reference closed: github.com/github/gitignore/pull/1529 · Issue #3 · ory/client-dotnet · GitHub
Skip to content

upstream reference closed: github.com/github/gitignore/pull/1529 #3

Open

Description

@github-actions

The upstream pull got closed. It is referenced in:

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

Activity

  1. added
    good first issueA good issue to tackle when being a novice to the project.
    help wantedWe are looking for help on this one.
    upstreamIssue is caused by an upstream dependency.
    on Jan 1, 2025
  2. github-actions commented on Oct 1, 2026

    @github-actions
    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 🙏✌️

  3. added
    staleFeedback from one or more authors is required to proceed.
    on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueA good issue to tackle when being a novice to the project.help wantedWe are looking for help on this one.staleFeedback from one or more authors is required to proceed.upstreamIssue is caused by an upstream dependency.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions