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

Create topic "OIDC" #4576

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Create topic "OIDC" #4576

merged 1 commit into from
Jan 16, 2025

Conversation

shaedrich
Copy link
Contributor

Please confirm this pull request meets the following requirements:

Which change are you proposing?

  • Suggesting edits to an existing topic or collection
  • Curating a new topic or collection
  • Something that does not neatly fit into the binary options above

Editing an existing topic or collection

I'm suggesting these edits to an existing topic or collection:

  • Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
  • Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

  • I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
  • My folder contains a *.png image (if applicable) and index.md
  • All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Together, oidc and openid-connect have more than 2k repositories

Something that does not neatly fit into the binary options above

  • My suggested edits are not about an existing topic or collection, or at least not a single one
  • My suggested edits are not about curating a new topic or collection, or at least not a single one
  • My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of your proposed changes.


Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

@shaedrich shaedrich requested a review from a team as a code owner January 11, 2025 02:33
@shaedrich
Copy link
Contributor Author

Btw, is there a reason why the "Issues" tab is disabled in this repository? It would be nice if one could report bugs there, especially, since some already have been reported in some PR comments, but it's easy for them to get buried there.

@tomthorogood
Copy link
Contributor

@shaedrich people unfortunately would use the issues tab to report general complaints/bugs across all of github, and we weren't able to manage this. The OSS support for topics/collections/explore is volunteer-run; there's no dedicated staff to help with communications in things like issues, etc. Therefore we have to keep the interactions minimal. We really appreciate your contributions! ❤️

@tomthorogood tomthorogood added this pull request to the merge queue Jan 16, 2025
Merged via the queue into github:main with commit e170f88 Jan 16, 2025
5 checks passed
@shaedrich
Copy link
Contributor Author

@tomthorogood Thanks for the clarification! So essentially, there's no way #3980 (comment) gets fixed, right?

@shaedrich shaedrich deleted the patch-3 branch January 16, 2025 16:19
@tomthorogood
Copy link
Contributor

@shaedrich There's definitely a chance. Thanks for raising it here (and for reporting in github/community!) There's no guaranteed timeline, but there are plenty of folks internally who love to help with stuff like this when they/we have time. I'll add this as an item that someone could pick up.

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

Successfully merging this pull request may close these issues.

2 participants