|
3 | 3 | # VersionTwo |
4 | 4 | Hackathon project: CLI tool to generate static planning view of issues for better team planning |
5 | 5 |
|
6 | | -# Problem we are solving |
7 | | -GitHub projects users are unable to easily associate issues across organizations with a project and particularly find having to manually add issues to the project board itself as a time consuming unnecessarily difficult task. |
8 | | - |
9 | | -We propose improving this interface by adding a simple HTTP page with an interactive Kanban which is able to aggregate a user provided selection of repos, projects, organizations and display them in a filterable way. |
10 | | - |
11 | | -# Getting Started |
12 | | -## Requirements and Setup |
13 | | -The following items are required to run the program. |
| 6 | +# 🚀 Getting Started |
| 7 | +## 📦 Requirements |
| 8 | +The following dependencies are required to run the program: |
14 | 9 | - Python 3.x |
| 10 | + - `brew install python3` |
15 | 11 | - Python `pyenv` and `pyenv-virtualenv` |
16 | 12 | - `brew install pyenv pyenv-virtualenv` |
17 | 13 | - GitHub Command Line Interface (CLI) `gh` |
| 14 | + - `brew install gh` |
| 15 | + |
| 16 | +## 💻 Setup |
18 | 17 | - Authentication through `gh auth login` |
19 | | - - Set the appropriate token permissions: `gh auth refresh --scopes read:project` |
| 18 | +- Set the appropriate token permissions: `gh auth refresh --scopes read:project` |
| 19 | +- Run `make install` inside the repo directory to configure the appropriate versions of dependencies. |
| 20 | + |
| 21 | +## 🛠 Usage |
| 22 | +To run the main script, change to the current directory of the script, then run: |
| 23 | + |
| 24 | +`python version2.py --output-file "<filename.json>" --temp-dir "<temp.dir>" --include-team <teamname>` |
| 25 | + |
| 26 | +See the `--help` menu for full list of filter functionality. |
20 | 27 |
|
21 | | -Run `make install` inside the repo directory to configure the appropriate versions of dependencies. |
| 28 | +# Background |
| 29 | +GitHub users have issues assigned to themselves or a team they are a member of. These issues can be viewed on a |
| 30 | +Project board, which captures the issues in swim lanes. The Project board can only automate with a single organization, |
| 31 | +meaning users who work in more than one org do not have a single location to view all issues. This leads to fragmented |
| 32 | +planning and execution. |
22 | 33 |
|
| 34 | +# Our Solution |
| 35 | +Our python script will query the GitHub API for all issues associated with the appropriate filters provided to the CLI |
| 36 | +tool. The output will be a static HTML page showing all issues in swim lanes. This provides a comprehensive overview |
| 37 | +of all issues the team or user has assigned. |
0 commit comments