11![ App icon] ( images/FullSizeIcon.png )
22
33# VersionTwo
4+
45Hackathon project: CLI tool to generate static planning view of issues for better team planning
56
6- # 🚀 Getting Started
7- ## 📦 Requirements
7+ ## 🚀 Getting Started
8+
9+ ### 📦 Requirements
10+
811The following dependencies are required to run the program:
12+
913- Python 3.x
1014 - ` brew install python3 `
1115- Python ` pyenv ` and ` pyenv-virtualenv `
12- - ` brew install pyenv pyenv-virtualenv `
16+ - ` brew install pyenv pyenv-virtualenv `
1317- GitHub Command Line Interface (CLI) ` gh `
1418 - ` brew install gh `
1519
16- ## 💻 Setup
20+ ### 💻 Setup
21+
1722- Authentication through ` gh auth login `
18- - Set the appropriate token permissions: ` gh auth refresh --scopes read:project `
19- - Note: The team must have ` read ` permissions on the Project Board in order to view the issues on the board.
20- - Set the ` GITHUB_TOKEN ` environment variable: ` export GITHUB_TOKEN=$(gh auth token) `
21- - Set the ` GITHUB_UNAME ` environment variable: ` export GITHUB_UNAME=$(gh auth status | grep "(GITHUB_TOKEN)" | cut -d " " -f9) `
23+ - Source the [ setup-gh.sh] ( src/setup-gh.sh ) script to configure your gh environment variables
24+
25+ ``` bash
26+ source src/setup-gh.sh # follow the prompts
27+ ```
28+
29+ - Sets the appropriate token scopes: ` read ` .
30+ - Note: The team must have ` read ` permissions on the Project Board in order to view the issues on the board.
31+ - Sets the ` GITHUB_TOKEN ` environment variable.
32+ - Sets the ` GITHUB_UNAME ` environment variable.
2233- Run ` make install ` inside the repo directory to configure the appropriate versions of dependencies.
2334
24- ## 🛠 Usage
35+ ### 🛠 Usage
36+
2537To run the main script, change to the current directory of the script, then run:
2638
2739` python version2.py --output-file "<filename.json>" --temp-dir "<temp.dir>" --include-project <project name> `
2840
2941See the ` --help ` menu for full list of filter functionality.
3042
31- # Background
43+ ## Background
44+
3245GitHub users have issues assigned to themselves or a team they are a member of. These issues can be viewed on a
3346Project board, which captures the issues in swim lanes. The Project board can only automate with a single organization,
3447meaning users who work in more than one org do not have a single location to view all issues. This leads to fragmented
3548planning and execution.
3649
37- # How does it work?
50+ ## How does it work?
3851
3952``` mermaid
4053%% A · System-Architecture Diagram (≤25 nodes)
@@ -52,7 +65,8 @@ classDef api fill:#e3f2fd,stroke:#2196f3;
5265classDef cli fill:#f1f8e9,stroke:#7cb342;
5366```
5467
55- # Our Solution
68+ ## Our Solution
69+
5670Our python script will query the GitHub API for all issues associated with the appropriate filters provided to the CLI
5771tool. The output will be a static HTML page showing all issues in swim lanes. This provides a comprehensive overview
58- of all issues the team or user has assigned.
72+ of all issues the team or user has assigned.
0 commit comments