Agree run / decision numbering with Tayyab and merge origin/master (OD-12)

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
java
Domain
tooling

Research direction

The issue points to layout.py and conflicting run and decision numbering across origin/master and the Step 4 branches. First compare those branches and the two ceiling rules, then get the team decision described in the issue before merging. Done means the numbering and ceiling rule are agreed and the merge is complete.

Written by the indexing model from the issue text.

Description

needs-umair step-4

R-032 … R-040 and D-069 mean different things on origin/master and the Step 4 branches; layout.py has two ceiling rules (D-072 and Tayyab's d052301). Team decision first, then the merge.

Dominant language
Java
Stars
0
Forks
0
Avg merge
6m
Merged PRs (30d)
7

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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 Umairishuman/BuildScan3D

All issues in Umairishuman/BuildScan3D

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.