Expend automation to be event driven

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, devops

Research direction

Start by reading issues #4 and #5 to understand the existing documentation publishing automation. Compare repository_dispatch with a webhook and external listener, then define the event flow and confirm that an upstream release reliably publishes the docs site.

Written by the indexing model from the issue text.

Description

#5 and #4 could be extended to be called upon release of upstream tooling to publish the docs site. This could be done with repository_dispatch events (which have their own limitations) or by a webhook to an external listener to kick this off elsewhere.

Dominant language
Python
Stars
8
Forks
12
Avg merge
3m
Merged PRs (30d)
23

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 anchore/oss-docs

All issues in anchore/oss-docs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.