You are an experienced software developer tasked with addressing a GitHub issue. Your goal is to analyze the issue, understand the codebase, and create a comprehensive plan to tackle the task. Follow these steps carefully:
<github_issue> #$ARGUMENTS </github_issue>
Analyze the code thoroughly until you feel you have a solid understanding of the context and requirements.
You are an AI assistant tasked with creating well-structured GitHub issues for feature requests, bug reports, or improvement ideas. Your goal is to turn the provided feature description into a comprehensive GitHub issue that follows best practices and project conventions.
First, you will be given a feature description and a repository URL. Here they are:
<feature_description> #$ARGUMENTS </feature_description>
Follow these steps to complete the task, make a todo list and think ultrahard:
| #!/bin/bash | |
| # Requires code2prompt to be installed: https://github.com/mufeedvh/code2prompt | |
| echo "Updating prompts" | |
| echo "Create output directory if it doesn't exist" | |
| mkdir -p "./50 Resources/57 Prompts/" | |
| echo "Generate mega prompt from literature notes" | |
| code2prompt "./30 Areas/32 Literature notes" --include "*.md" --tokens --output="./50 Resources/57 Prompts/Literature notes.md" |
| --- | |
| creation date: <% tp.file.creation_date() %> | |
| tags: DailyNote <% tp.file.title.split('-')[0] %> | |
| --- | |
| modification date: <%+ tp.file.last_modified_date("dddd Do MMMM YYYY HH:mm:ss") %> // This doesn't currently work in front matter, hoping that gets fixed. | |
| # <% tp.file.title %> | |
| << [[<% tp.date.now("YYYY-MM-DD", -1, tp.file.title, "YYYY-MM-DD") %>]] | [[<% tp.date.now("YYYY-MM-DD", 1, tp.file.title, "YYYY-MM-DD") %>]]>> |
Latest News: http://site.api.espn.com/apis/site/v2/sports/football/college-football/news
Latest Scores: http://site.api.espn.com/apis/site/v2/sports/football/college-football/scoreboard
| # This is a template .gitignore file for git-managed WordPress projects. | |
| # | |
| # Fact: you don't want WordPress core files, or your server-specific | |
| # configuration files etc., in your project's repository. You just don't. | |
| # | |
| # Solution: stick this file up your repository root (which it assumes is | |
| # also the WordPress root directory) and add exceptions for any plugins, | |
| # themes, and other directories that should be under version control. | |
| # | |
| # See the comments below for more info on how to add exceptions for your |