3tractorrides / release-notes-formatter

MIT License
0 stars 0 forks source link

Sweep: Add a section in the readme about usage #10

Closed 3tractorrides closed 10 months ago

3tractorrides commented 10 months ago

Details

Add a section to the readme about how to use this script

Checklist - [X] Modify `README.md` βœ“ https://github.com/3tractorrides/release-notes-formatter/commit/ed8fe8ef394b664f83338336b1ddc0656981d6e3 [Edit](https://github.com/3tractorrides/release-notes-formatter/edit/sweep/add_a_section_in_the_readme_about_usage/README.md#L39-L39) - [X] Running GitHub Actions for `README.md` βœ“ [Edit](https://github.com/3tractorrides/release-notes-formatter/edit/sweep/add_a_section_in_the_readme_about_usage/README.md#L39-L39)
sweep-ai[bot] commented 10 months ago

πŸš€ Here's the PR! #11

See Sweep's progress at the progress dashboard!
⚑ Sweep Basic Tier: I'm using GPT-4. You have 2 GPT-4 tickets left for the month and 3 for the day. (tracking ID: bc3829c56e)

For more GPT-4 tickets, visit our payment portal. For a one week free trial, try Sweep Pro (unlimited GPT-4 tickets).

[!TIP] I can email you next time I complete a pull request if you set up your email here!


Actions (click)

GitHub Actionsβœ“

Here are the GitHub Actions logs prior to making any changes:

Sandbox logs for 432b43d
Checking README.md for syntax errors... βœ… README.md has no syntax errors! 1/1 βœ“
Checking README.md for syntax errors...
βœ… README.md has no syntax errors!

Sandbox passed on the latest main, so sandbox checks will be enabled for this issue.


Step 1: πŸ”Ž Searching

I found the following snippets in your repository. I will now analyze these snippets and come up with a plan.

Some code snippets I think are relevant in decreasing order of relevance (click to expand). If some file is missing from here, you can mention the path in the ticket description. https://github.com/3tractorrides/release-notes-formatter/blob/432b43d28c59ec6cfd3fa15359ea6ed05ba4bc79/README.md#L30-L38

Step 2: ⌨️ Coding

--- 
+++ 
@@ -38,6 +38,15 @@
 1. Rrom a terminal, run `python3 main.py`
 1. Observe the formatted results in `output.md`

+## Using the pull_commits_for_release.py script
+
+This script is used to pull commits for a release. It takes a release number as an argument and outputs a list of commits associated with that release.
+
+### Instructions for use:
+1. From a terminal, run `python3 pull_commits_for_release.py ` where `` is the number of the release you want to pull commits for.
+2. The script will output a list of commits associated with the specified release.
+3. Before running the script, ensure you have Python 3 installed and are in the root directory of the repository.
+
 ## Tests

 This project includes unit tests found in `test_main.py`. Any changes, additions, or removals in `main.py` must be accounted for in the tests. 

Ran GitHub Actions for ed8fe8ef394b664f83338336b1ddc0656981d6e3:


Step 3: πŸ” Code Review

I have finished reviewing the code for completeness. I did not find errors for sweep/add_a_section_in_the_readme_about_usage.


πŸŽ‰ Latest improvements to Sweep:


πŸ’‘ To recreate the pull request edit the issue title or description. To tweak the pull request, leave a comment on the pull request. Join Our Discord