Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update contribution guide #636

Merged
merged 2 commits into from
Oct 26, 2018
Merged

Conversation

Zlopez
Copy link
Contributor

@Zlopez Zlopez commented Oct 12, 2018

When doing first release using towncrier I noticed some missing things in contribution guide.

So this PR is addressing them.

@codecov-io
Copy link

codecov-io commented Oct 12, 2018

Codecov Report

Merging #636 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #636   +/-   ##
=======================================
  Coverage   90.54%   90.54%           
=======================================
  Files          56       56           
  Lines        2698     2698           
  Branches      355      355           
=======================================
  Hits         2443     2443           
  Misses        197      197           
  Partials       58       58

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0994242...75a5a44. Read the comment docs.

Copy link

@bowlofeggs bowlofeggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a few small suggestions. Let me know when you are ready and I'm happy to mark it approved.

@@ -132,6 +132,11 @@ another ``psql`` commands::

For additional ``psql`` commands see ``man psql``.

To run cron job in vagrant container run these commands::

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To run cron job in vagrant container run these commands::
To run the cron job in the Vagrant guest, run these commands::

To run cron job in vagrant container run these commands::

$ workon anitya
$ ANITYA_WEB_CONFIG=/home/vagrant/anitya.toml python files/anitya_cron.py

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could make it so that the workon anitya adds ANITYA_WEB_CONFIG=/home/vagrant/anitya.toml to the environment automatically.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added it to bashrc for vagrant guest.

@@ -209,17 +214,25 @@ If you are a maintainer and wish to make a release, follow these steps:
1. Change the version in ``anitya.__init__.__version__``. This is used to set the
version in the documentation project and the setup.py file.

2. Generate the changelog by running ``towncrier``.
2. Add any missing news fragment to ``news`` folder

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Add any missing news fragment to ``news`` folder
2. Add any missing news fragments to the ``news`` folder.

3. Generate the changelog by running ``towncrier``.

.. note::
If you added any news fragment in previous step you could see ``towncrier``

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you added any news fragment in previous step you could see ``towncrier``
If you added any news fragment in the previous step, you might see ``towncrier``


.. note::
If you added any news fragment in previous step you could see ``towncrier``
complaining about removing them, because these are not commited in git.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
complaining about removing them, because these are not commited in git.
complaining about removing them, because they are not committed in git.

.. note::
If you added any news fragment in previous step you could see ``towncrier``
complaining about removing them, because these are not commited in git.
Just ignore this and remove them manually, release notes will be generated

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Just ignore this and remove them manually, release notes will be generated
Just ignore this and remove them manually; release notes will be generated


4. Tag a release with ``git tag -s v<version>``.
5. Tag a release with ``git tag -s <version>``.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+100

Copy link

@bowlofeggs bowlofeggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I recommend squashing the commits before merging.

@Zlopez
Copy link
Contributor Author

Zlopez commented Oct 24, 2018

squash

bowlofeggs
bowlofeggs previously approved these changes Oct 24, 2018
Copy link

@bowlofeggs bowlofeggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one also fails lint.

@Zlopez
Copy link
Contributor Author

Zlopez commented Oct 25, 2018

The PR fixing the lint issue was merged, so I'm doing a rebase to fix also this PR.

@mergify mergify bot merged commit 761b452 into fedora-infra:master Oct 26, 2018
@Zlopez Zlopez deleted the release_guide branch October 29, 2018 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants