Update documentation automatically from TravisCI for new releases

Open
#38 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
ci-cd, documentation, release

Research direction

Start by examining the existing TravisCI release workflow and how the PyPI package is currently updated. Identify where documentation updates are handled manually and define a release path that performs them automatically. Done means new releases update the documentation without a separate manual step.

Written by the indexing model from the issue text.

Description

It can be easy to forget a manual step like this, and would be better if this was handled by TravisCI in the same way that the PyPI package is automatically updated for new releases.

Dominant language
Python
Stars
37
Forks
14
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from azavea/python-omgeo

All issues in azavea/python-omgeo

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.