Trolley syncs issues from CSVs to Github and to sync projects between Github and Trello.
Trolley is a useful tool for loading an initial set of issues, labels, and milestones on github.
Trolley was written to also help me manage a few projects where I need to selectively sync Issues and boards between Trello and Github.
By Roland zh (Own work) [CC BY-SA 3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via Wikimedia Commons
Installation
$ pip install trolley
Usage
Example trolley.yml
github:
username: 'username'
password: 'password'
org: 'github'
repo: 'gitignore'
trello:
app_key: 'get-this-from-trello'
app_secret: 'get-this-from-trello'
auth_token: 'get-this-from-trello'
board_id: 'your-board-id-sha'
default_list: 'Uncategorized'
Usage
$ trolley --conf trolley.yml --help
$ trolley --conf trolley.yml create_github_issues
Commands
- bootstrap
Sets up github with some sensible defaults.
- close_existing_github_issues
Close all existing GitHub issues.
- create_github_issues
Create GitHub issues from a CSV file.
- create_github_labels
Create GitHub labels from a CSV file.
- create_github_milestones
Create GitHub milestones from a CSV file.
- create_trello_cards
Create Trello cards from a CSV file.
- create_trello_labels
Create Trello labels from a CSV file.
- create_trello_lists
Create Trello lists from a CSV file.
- delete_existing_github_labels
Delete labels from GitHub repo.
- delete_existing_github_milestones
Delete milestones from GitHub repo.
- sync_github_issues_to_trello_cards
Convert your GitHub issues to Trello cards.
- sync_trello_cards_to_github_issues
Convert your Trello cards to GitHub issues.
Object Overview
Github |
Trello |
Notes |
|---|---|---|
Org / Repo |
Board |
== |
Issues |
Cards |
== |
Labels |
Labels |
== |
Milestones |
||
Lists |
Milestones and Lists may be mapped together but they are fundamentally treated very differently.
Future features
Needs allowed list / blocked list for handling via labels.
This is basically “works for me” but it needs error handling.
Inspiration
This project shares ideas from the following projects:
The CSV bits via: https://github.com/nprapps/app-template
Metadata
Release files for trolley 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| trolley-0.1.5.tar.gz | 7.8 kB | Without provenance | Details for trolley-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| trolley-0.1.5-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for trolley-0.1.5-py2.py3-none-any.whl |
Total release size: 13.3 kB
Release files / trolley-0.1.5.tar.gz
| Download URL | trolley-0.1.5.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6d6d42807c2b893234a1d91cdb3eb45232cf697a25662f66235a186dc4529a1
|
|
BLAKE2b-256 checksum How to use checksums |
247dc128ace91b23191e3e77dbb347428c5132712c0cf89a0c74ea13f9f261d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / trolley-0.1.5-py2.py3-none-any.whl
| Download URL | trolley-0.1.5-py2.py3-none-any.whl |
|---|---|
| Size | 5.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d6a194609a57843f0f3db76d7a843d32a9ecf678cdde9f82116cc1d7e227d468
|
|
BLAKE2b-256 checksum How to use checksums |
aae107abddb6de14aec0cdb8b22f2af0e307f8f166b84fb6f16fda9e5a19d30f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for trolley 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.