playfulprogramming / playfulprogramming/hoof

Support importing author, collection, and post data from a pull request webhook

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

Nobody has claimed this yet.

backend
Dominant language
TypeScript
Stars
9
Forks
7
Avg merge
1d 2h
Merged PRs (30d)
23

Description

Note: See the sub-issues for actual tasks. The description below is vague notes / future planning beyond the scope of this issue.


When someone creates a pull request to the content repository (to be created / split from the Astro codebase in the future), hoof should:

  • Look up the author of the pull request
  • Determine if they have an account in the CMS (TBD: how?)
    • If not, create a profile/user record in the DB
      • TBD: should they be prompted to complete oauth to create an account via PR comment?
  • Obtain the forked repo/branch from the PR webhook event
  • Import the post under the author's profile as a draft
    • TBD: We need the frontend to expose a no-index page for viewing a draft post from the API
  • Send a build status back to the PR to indicate if the import was successful

If the same post is later sent via a push webhook from main, the post should be marked as published with the webhook date as the timestamp.

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.

Research direction

No files or tests are named, and the issue says the actual tasks belong in sub-issues. Start by finding those sub-issues and the pull-request and push webhook entry points, then map the CMS/database import and PR status flows. Done criteria are not yet scoped beyond author lookup, draft import, build status, and later publication.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, backend, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.