Research: Deal with multiple master merges.

Open
#13 1 comment 0 reactions 0 assignees View on GitHub

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
javascript
Domain
ci-cd, devops, release

Research direction

Start by inspecting the repository's deployment and build workflow, then reproduce or trace what happens when multiple commits merge to master in quick succession. Determine whether an older build can be deployed or whether master has a separate build, and document the observed behavior. If outdated builds can deploy, define and record a mitigation strategy.

Written by the indexing model from the issue text.

Description

  • Research and confirm what happens if we have multiple immediate merges to master. Do old builds get deployed? Or is there a separate master build?
  • If old builds can get deployed, figure out a mitigation strategy. Require current to master, etc?
Dominant language
JavaScript
Stars
7
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 FormidableLabs/formideploy

All issues in FormidableLabs/formideploy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.