We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cvelistV5/.github/workflows/update.yml
Lines 48 to 49 in bb74fe0
https://github.com/CVEProject/cvelistV5/commit/bb74fe0f2f6fabe1d25aec108530e45a1b7fc644.patch From: cvelistV5 Github Action <[email protected]>
Should the first 'h' be capitalized? (GitHub instead of Github)
Is there any potential advantage in using an email address that you control? For example:
https://github.com/CVEProject/cvelist/commit/f47fcda074db819cda8db7213116c29e21e15e14.patch From: CVE Team <[email protected]>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
cvelistV5/.github/workflows/update.yml
Lines 48 to 49 in bb74fe0
results in this data format in the patch view of a commit:
Should the first 'h' be capitalized? (GitHub instead of Github)
Is there any potential advantage in using an email address that you control? For example:
The text was updated successfully, but these errors were encountered: