Asana task's title and note is created as Github issue. The comments and attachments of the task are added as a comment to the Github issue. AsanaToGithub supports linking the Asana task and Github issue together by means of adding links in the comments at both sites.
Features
--------
#. You can copy incomplete and completed tasks.
#. Tasks can be copied in batch or interactively.
#. You can copy Asana comments and attachments to the Github issue which can be disabled.
#. A comment is added to Asana task which has link to the Github issue. This can be disabled.
#. After copy, tag and labels are applied to the Asana task and Github issue respectively. This too can be disabled.
Example
-------
This is a `sample Github issue <https://github.com/talha131/AsanaToGithub/issues/1>`_ copied from Asana using AsanaToGithub.
1 maintainer
Metadata
1 maintainer
Release files for AsanaToGithub 1.0.0
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 | |
|---|---|---|---|---|
| AsanaToGithub-1.0.0.tar.gz | 5.3 kB | Without provenance | Details |
Release files / AsanaToGithub-1.0.0.tar.gz
| Download URL | AsanaToGithub-1.0.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2e6df63eccff41542e2e244fd7f86da5e2e6f736656954937940418f2b2595a
|
|
BLAKE2b-256 checksum How to use checksums |
9c34d19a9f575e949736121c90d6557c83ef91bf223ed553ae21d7c915139eea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for AsanaToGithub 1.0.0
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.
