{"id":19292132,"url":"https://github.com/nasa-pds/lasso-issues","last_synced_at":"2026-02-06T21:02:49.390Z","repository":{"id":182312749,"uuid":"668315938","full_name":"NASA-PDS/lasso-issues","owner":"NASA-PDS","description":"Utilities for wrapping GitHub API for creating specific data structures and reports from GitHub issues","archived":false,"fork":false,"pushed_at":"2026-02-02T23:05:26.000Z","size":6157,"stargazers_count":0,"open_issues_count":18,"forks_count":1,"subscribers_count":6,"default_branch":"main","last_synced_at":"2026-02-03T06:54:44.225Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/NASA-PDS.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".github/CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":"NOTICE.txt","maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2023-07-19T14:13:15.000Z","updated_at":"2026-02-02T17:20:49.000Z","dependencies_parsed_at":"2025-09-10T19:31:17.803Z","dependency_job_id":"2c0d3b2b-90c2-4b5d-be63-a43fa0fb8c92","html_url":"https://github.com/NASA-PDS/lasso-issues","commit_stats":null,"previous_names":["nasa-pds/lasso-issues"],"tags_count":9,"template":false,"template_full_name":null,"purl":"pkg:github/NASA-PDS/lasso-issues","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Flasso-issues","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Flasso-issues/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Flasso-issues/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Flasso-issues/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/NASA-PDS","download_url":"https://codeload.github.com/NASA-PDS/lasso-issues/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/NASA-PDS%2Flasso-issues/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29175829,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-06T20:14:21.878Z","status":"ssl_error","status_checked_at":"2026-02-06T20:14:21.443Z","response_time":59,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-09T22:29:25.949Z","updated_at":"2026-02-06T21:02:49.384Z","avatar_url":"https://github.com/NASA-PDS.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# PDS Lasso Issues\n\nThe PDS Lasso Issues package provides utilities handle issues on GitHub. It provides these commands:\n\n- `milestones`\n- `pds-issues`\n- `move-issues`\n- `pds-labels`\n- `add-version-label-to-open-bugs`\n- `pds-scheduler-themes`\n\nPlease visit our website at: https://nasa-pds.github.io/lasso-issues\n\nIt may have useful information for developers and end-users.\n\n\n## Prerequisites\n\nInstalling this software requires `git` to be present on the target systme.\n\n\n## User Quickstart\n\nInstall with:\n\n    pip install lasso-issues\n\n\n### Using pds-scheduler-themes\n\n### pds-issues\n\nGenerate issue reports in various formats (Markdown, RST, CSV).\n\n```bash\n# Set your GitHub token\nexport GITHUB_TOKEN=your_token_here\n\n# Generate a Markdown planning report\npds-issues --format=md --github-org=NASA-PDS\n\n# Generate an RST Release Description Document (RDD)\npds-issues --format=rst --build=B15.1 --github-org=NASA-PDS\n\n# Generate an RST RDD with component grouping (groups repos by product)\npds-issues --format=rst --build=B15.1 --github-org=NASA-PDS --group-by-component\n\n# Generate for specific repositories only\npds-issues --format=rst --build=B15.1 --github-org=NASA-PDS --github-repos validate registry\n```\n\n#### Component Grouping\n\nWhen using `--group-by-component`, repositories are grouped by their product/component as defined in `conf/pds-products.yaml`. This produces a hierarchical document structure:\n\n- **Component sections** (H2) containing related repositories\n- **Repository sections** (H3) with their issues\n- **Summary metrics table** at the end showing issue counts by component\n\n#### Output Formats\n\n- `--format=md`: Markdown planning or known bugs report\n- `--format=rst`: reStructuredText Release Description Document with theme trees\n- `--format=metrics`: Summary metrics output\n- `--format=csv`: CSV export for test management (TestRail integration)\n\n### milestones\n\nManage GitHub milestones across repositories.\n\n### move-issues\n\nMigrate issues between repositories.\n\n### pds-labels\n\nBulk label management across organization repositories\nThe `pds-scheduler-themes` command automates creation of release theme issues from CSV schedule files.\n\n**Prerequisites:**\n- GitHub CLI (`gh`) must be installed and authenticated\n- Write access to target NASA-PDS repositories\n\n**Basic Usage:**\n\n```bash\n# Preview what would be created (dry-run mode)\npds-scheduler-themes --csv-file schedule.csv --build-number 17 --dry-run\n\n# Create the issues\npds-scheduler-themes --csv-file schedule.csv --build-number 17\n\n# With debug logging\npds-scheduler-themes --csv-file schedule.csv --build-number 17 --debug\n```\n\n**CSV Format:**\n\nThe CSV file should contain these columns:\n- **Title**: Issue title (will be prefixed with build number, e.g., \"B17 Release Planning\")\n- **Repo**: Repository name in format `NASA-PDS/repo-name`\n- **Start Date**: Start date in YYYY-MM-DD format (e.g., \"2025-09-05\")\n- **End Date**: End date in YYYY-MM-DD format (e.g., \"2025-10-16\")\n- **Description**: Issue description text\n- **Checklist**: Semicolon-delimited checklist items (e.g., \"Task 1;Task 2;Task 3\")\n- **GitHub Project Product**: Product name for project metadata (optional)\n\n**Features:**\n- Automatically prefixes issue titles with build number (e.g., \"B17\")\n- Checks for duplicate issues and skips if already exists\n- Creates build labels (e.g., \"B17\") if they don't exist\n- Adds issues to NASA-PDS/6 project and build-specific projects\n- Applies labels: `theme`, `Epic`, `i\u0026t.skip`, and build label\n- Converts checklist items to markdown checkboxes\n\n**Output:**\n\nThe tool provides a summary showing:\n- ✓ Created issues with URLs\n- ⊙ Skipped issues (already exist)\n- ✗ Failed issues\n\nSee `examples/b17_schedule_prep_spreadsheet.csv` for a sample CSV file.\n\n\n## Code of Conduct\n\nAll users and developers of the NASA-PDS software are expected to abide by our [Code of Conduct](https://github.com/NASA-PDS/.github/blob/main/CODE_OF_CONDUCT.md). Please read this to ensure you understand the expectations of our community.\n\n\n## Development\n\nTo develop this project, use your favorite text editor, or an integrated development environment with Python support, such as [PyCharm](https://www.jetbrains.com/pycharm/).\n\n\n### Contributing\n\nFor information on how to contribute to NASA-PDS codebases please take a look at our [Contributing guidelines](https://github.com/NASA-PDS/.github/blob/main/CONTRIBUTING.md).\n\n\n### Installation\n\nInstall in editable mode and with extra developer dependencies into your virtual environment of choice:\n\n    pip install --editable '.[dev]'\n\nConfigure the `pre-commit` hooks:\n\n    pre-commit install\n    pre-commit install -t pre-push\n    pre-commit install -t prepare-commit-msg\n    pre-commit install -t commit-msg\n\nThese hooks check code formatting and also aborts commits that contain secrets such as passwords or API keys. However, a one time setup is required in your global Git configuration. See [the wiki entry on Git Secrets](https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Git-and-Github-Guide#git-secrets) to learn how.\n\n\n### Packaging\n\nTo isolate and be able to re-produce the environment for this package, you should use a [Python Virtual Environment](https://docs.python.org/3/tutorial/venv.html). To do so, run:\n\n    python3 -m venv venv\n\nThen exclusively use `venv/bin/python`, `venv/bin/pip`, etc. Or, \"activate\" the virtual environment by sourcing the appropriate script in the `venv/bin` directory.\n\nIf you have `tox` installed and would like it to create your environment and install dependencies for you run:\n\n    tox --devenv \u003cname you'd like for env\u003e -e dev\n\nDependencies for development are specified as the `dev` `extras_require` in `setup.cfg`; they are installed into the virtual environment as follows:\n\n    pip install --editable '.[dev]'\n\nAll the source code is in a sub-directory under `src`.\n\n\n### Tooling\n\nThe `dev` `extras_require` included in the template repo installs `black`, `flake8` (plus some plugins), and `mypy` along with default configuration for all of them. You can run all of these (and more!) with:\n\n    tox -e lint\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnasa-pds%2Flasso-issues","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnasa-pds%2Flasso-issues","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnasa-pds%2Flasso-issues/lists"}