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 vulnerability databases collection #4601

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

m3lixir
Copy link
Contributor

@m3lixir m3lixir commented Jan 28, 2025

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

I think it’s important for people to be aware of the original vulnerability databases that set the foundation for this field, while also highlighting newer, growing ones. Having this context is essential for any developer interested in understanding and managing vulnerabilities in their applications effectively.

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.

@m3lixir m3lixir requested a review from a team as a code owner January 28, 2025 08:57
@jmeridth
Copy link
Member

@m3lixir please merge main into your branch and it'll fix that broken test.

@m3lixir m3lixir reopened this Jan 28, 2025
@jmeridth jmeridth added this pull request to the merge queue Jan 28, 2025
Merged via the queue into github:main with commit 096b1b2 Jan 28, 2025
10 checks passed
@m3lixir m3lixir deleted the collections-vdbs branch January 28, 2025 20:56
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