Cutting out v0.1.3a1 PyPI release after #100 gets merged

[gridhead]

This issue ticket is a follow-up to the discussion with @jwflory during our 1:1.

Once #100 gets merged, I will push out a v0.1.3a1 release on PyPI for folks to test.

Here are the steps to test things out.

1. Create a temporary directory named test.

   $ mkdir test
   

2. Make that directory your current working directory.

   $ cd test
   

3. Create a virtual environment there.

   $ python -m venv venv
   

4. Enable the recently created virtual environment.

   $ source venv/bin/activate
   

5. Install the specific version of pagure-exporter.

   (venv) $ pip install pagure_exporter==0.1.3a1
   

6. Run commands to test the usability of the installation.

   (venv) $ pagure-exporter ...
   

7. Disable the virtual environment.

   (venv) $ deactivate
   

8. Purge the temporary directory named test.

   $ rm -rf ../test
   

Please let us track the oopsies related to the said package here.

[gridhead]

Ok, #100 was merged and I have pushed a new alpha release on PyPI.

https://pypi.org/project/pagure-exporter/0.1.3a1/

Go on, give it a try.

[jwflory]

@gridhead I will wait until #96 is implemented to test this out. I have a lot going on this month with Flock and other deadlines, and my urgent use case was the Mentored Projects repository. Since we have gone ahead with using Pagure for this year's internships, I am not in a crunch anymore. I would still like to use this for the Community Operations Pagure repo, but you can also test that repo out on your end (w.r.t. API rate limits) since everything is already public.