19af1838b9
* Completed List cmd and added API calls * Minor comments and add delete code to pass linting * Typo in descriptions * Minor comments * Validations * Validations-1 * improved branch flag validation * removed build * working after refactory with bad names * Command working, test not working * Corrected creation of service * Finalized structure using service * Deleted tests * cleanup * cleanup * cleanup * removed space with tab * aligned types in model.go * Update model.go * resolved comments * Refactor * removed long descriptions * Working incomplete tests * Completed tests * cleanup * checks * CI and release workflows * PR comments * PR comments * minor comment issue * minor comment issue * updated tests to work with workflow * Updated tests to support new option service * Improved eror handling for list * Improved error handling * Printing error in restclient * Nil in rest client * reverting changes * Release.md * Updates docs * Updates docs * Upgraded go-gh * added env in workflow * reusing rest client error * reusing sankalps fix for windows workflow * Revert "reusing sankalps fix for windows workflow" This reverts commit dfb1a94305b94b16a720bff599dba755f4a96175. * Other imp files for release * security.md * Updated contribution guidelines * Updated numberings to start with 1 * Update README.md (#15) * Update README.md * Update README.md * Update README.md * Updated contributing.md Co-authored-by: Sankalp Kotewar <kotewar@github.com> Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com>
32 lines
1.7 KiB
Markdown
32 lines
1.7 KiB
Markdown
Thanks for helping make GitHub safe for everyone.
|
|
|
|
## Security
|
|
|
|
GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
|
|
|
|
Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
|
|
|
|
## Reporting Security Issues
|
|
|
|
If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
|
|
|
|
**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
|
|
|
|
Instead, please send an email to opensource-security[@]github.com.
|
|
|
|
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
|
|
|
|
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
|
|
* Full paths of source file(s) related to the manifestation of the issue
|
|
* The location of the affected source code (tag/branch/commit or direct URL)
|
|
* Any special configuration required to reproduce the issue
|
|
* Step-by-step instructions to reproduce the issue
|
|
* Proof-of-concept or exploit code (if possible)
|
|
* Impact of the issue, including how an attacker might exploit the issue
|
|
|
|
This information will help us triage your report more quickly.
|
|
|
|
## Policy
|
|
|
|
See [GitHub's Safe Harbor Policy](https://docs.github.com/en/github/site-policy/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)
|