You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# This is the dependabot configuration file that automates dependency updates
2
2
# Updates section configures how dependabot should handle dependency updates:
3
-
# - Monitors GitHub Actions workflow dependencies in the root directory
3
+
# - Monitors pip dependencies in the planventure-api directory
4
4
# - Checks for updates weekly
5
5
#
6
-
# Learn more at https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-the-dependabotyml-file
This repository serves as a template for creating a walkthrough. Follow the steps below to get started.
3
+
You can build along with me in this [Youtube video]() or read this [blog post]().
4
4
5
-
## Getting Started
5
+

6
+

6
7
7
-
1. Clone this repository.
8
-
2. Update the documentation in the `docs` folder (including the `README.md` folder).
9
-
3. Customize the code and other content as needed.
10
-
4. Update the `SUPPORT.md` file with the appropriate information.
11
-
5. Review the default LICENSE (MIT), CODE_OF_CONDUCT, and CONTRIBUTING files to ensure they meet your needs. These use the samples provided as part of the OSPO release process.
12
-
6. Update the `README.md` file in the repository root with the appropriate information. You can find an example at [github-samples/game-of-life-walkthrough](https://github.com/github-samples/game-of-life-walkthrough).
13
-
7. When you are ready to publish the repository, please make sure that the Git history is clean. Then, raise an issue for a 'sample release' at [https://github.com/github/open-source-releases](https://github.com/github/open-source-releases).
8
+
# Planventure API 🚁
9
+
A Flask-based REST API backend for the Planventure application.
10
+
11
+
## Prerequisites
12
+
Before you begin, ensure you have the following:
13
+
14
+
- A GitHub account - [sign up for FREE](https://github.com)
15
+
- Access to GitHub Copilot - [sign up for FREE](https://gh.io/gfb-copilot)!
16
+
- A Code Editor - [VS Code](https://code.visualstudio.com/download) is recommended
17
+
- API Client (like [Bruno](https://github.com/usebruno/bruno))
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).
6
+
7
+
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.
8
+
9
+
## Reporting Security Issues
10
+
11
+
If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
12
+
13
+
**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
14
+
15
+
Instead, please send an email to opensource-security[@]github.com.
16
+
17
+
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
18
+
19
+
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
20
+
* Full paths of source file(s) related to the manifestation of the issue
21
+
* The location of the affected source code (tag/branch/commit or direct URL)
22
+
* Any special configuration required to reproduce the issue
23
+
* Step-by-step instructions to reproduce the issue
24
+
* Proof-of-concept or exploit code (if possible)
25
+
* Impact of the issue, including how an attacker might exploit the issue
26
+
27
+
This information will help us triage your report more quickly.
28
+
29
+
## Policy
30
+
31
+
See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms)
0 commit comments