jaberg / jaberg/planzero

Deploy un-merged branches, perhaps as a replacement for "DRAFT Status"

Open
#80 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1
Forks
1
Avg merge
15d 20h
Merged PRs (30d)
1

Description

I'm not sure exactly how it might work with Fly.io, but it might be nice to be able to view the posts that have been authored on an unmerged branch such as "agrivoltaics-strategy", at urls such as e.g.
"agrivolatics-strategy.planzero.ca/scenarios".

Perhaps also there might be a rule / policy that the main branch doesn't have any posts in Draft.

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, tests, or deployment entry points are named. Start by documenting how the project currently deploys through Fly.io and how branches map to deployed URLs; done would mean a concrete, agreed design for viewing unmerged branch posts and handling drafts on the main branch.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.