This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Create GitHub issues based on local templates.

This is useful for pushing, for example, a set of checklists with per-item issues grouped by milestone. The template directory structure is:

.
|-- milestone-1
|   |-- README.md
|   |-- issue-1.1.md
|   |-- issue-1.2.md
|   ...
|-- milestone-2
|   |-- README.md
|   |-- issue-2.1.md
|   |-- issue-2.2.md
|   ...
...

Both the README.md and per-issue files have a summary line (which may optionally include Atx-style headers) followed by a blank line and an optional body. Milestone bodies are plain text, while issue bodies are GitHub flavored Markdown, For example, if you want each of your product to have a joel milestone tracking the Joel Test, you might have a joel/README.md with:

# joel

Keep track of how well the project handles the Joel Test [1].

[1]: http://www.joelonsoftware.com/articles/fog0000000043.html

And per-feature issue milestones like joel/source-control.md:

# Do you use source control?

I've used commercial source control packages, and I've used CVS,
which is free, and let me tell you, CVS is fine...

Of course, you probably can’t copy Joel’s text wholesale into your issue files, so you’d want to make your own summaries. Then run:

# github-push-issues.py [options] /path/to/your/template/directory

Or:

# github-push-issues.py [options] https://example.com/url/for/template.zip

The latter is useful if you have your template directory structure hosted online in a version control system that supports tar or zip archive snaphots.

Release History

Release History

0.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
github-push-issues-0.3.tar.gz (5.8 kB) Copy SHA256 Checksum SHA256 Source Apr 16, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting