Maker Project Parts with Git and GitHub Workflow: A 2027 Project Guide

Use a familiar campus workflow to practise Git and GitHub Workflow: maker project parts. The user is a student maker-team lead, and the first question is: How many issued parts are allocated by project? The deliverable is a reviewable change history with a visible rule and repeatable evidence behind its output.

This is a 2027 study-edition project brief. All example records and operational situations are fictional. Start with basic Git and GitHub Workflow knowledge, the ability to inspect structured data and a local practice environment. The complete first version should answer the stated question before adding accounts, real integrations or additional screens.

Define the project rule

Issued part counts describe outstanding allocations in this simple model. Returns change the state of a request, and partial returns require a separate quantity model rather than an unexplained status flip. For this exercise, one row represents one part_request. The stable key is record_id; project_name is the grouping or filtering label. The numeric part_count field uses parts. Accepted states are requested, issued, returned.

The summary selects status issued and applies sum to the selected numeric values. Keep this definition visible in the interface, response or report so another learner can reproduce it. Use positive finite values in the starter fixture and define any future zero or missing-value policy explicitly.

Choose the Git and GitHub Workflow approach

Break the work into changes that a reviewer can understand: fixture, validation, implementation and tests. Inspect the diff before committing and keep generated outputs out unless they are deliberate deliverables. Practice resolving a conflict on a disposable branch. Explain the difference between a local commit, a remote push and a deployed application.

The three design decisions to explain in your project notes are:

• Small coherent commits. Apply this choice to part_request records and explain its effect on part_count.
• Diff review before commit. Apply this choice to part_request records and explain its effect on part_count.
• Deliberate merge-conflict resolution. Apply this choice to part_request records and explain its effect on part_count.

Work through a small sample

The three records below are deliberately small enough to inspect by hand. They are a compact specification for the data shape and expected result, and can later be expanded into a larger synthetic fixture.

[
  {
    "record_id": "maker-project-parts-01",
    "project_name": "Sensor Display",
    "part_count": 2,
    "status": "issued",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "maker-project-parts-02",
    "project_name": "Desk Timer",
    "part_count": 1,
    "status": "requested",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "maker-project-parts-03",
    "project_name": "Mini Weather Board",
    "part_count": 3,
    "status": "issued",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match issued. Their part_count values are 2 and 3; the full-fixture result is 5 parts, with 2 matching records. Selecting project_name = Sensor Display leaves the first record, so the result becomes 2 parts, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "sum",
  "value": 5,
  "unit": "parts"
}

Check the result by project_name

The overall figure answers the all-records version of the question. Grouping by project_name produces the following separate expectations, using the same issued rule. The middle group has a record in the source fixture but no qualifying observation.

Use this breakdown when answering the group-level question. Compare like-for-like units and keep the matching count visible, especially for averages. A different filter changes which records enter the calculation; it does not change the meaning of the metric.

The code blocks describe sample data and an expected result. Implement the surrounding feature using the installed version of your chosen tools, then save the actual run evidence separately from these expectations.

Build the feature in three passes

1. Create a reviewable project boundary

Start a disposable branch for the part_request exercise. Add the fixture and a short explanation of project_name, part_count and allowed states. Keep environment-specific data out of the change so another learner can reproduce the project.

2. Develop through coherent revisions

Commit the validation, the issued-only sum, and its tests as understandable changes. Review the diff after each step. The result in parts should be traceable to a particular fixture and source revision, making a regression easier to locate.

3. Practice review and recovery

Make two small conflicting edits to the same rule on local practice branches. Resolve the conflict by preserving the documented acceptance test. Verify the final result from a fresh checkout and explain what remains local, pushed or deployed.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: A partially returned request is marked fully returned without quantity evidence. First reproduce it against the fixture, then identify the smallest rule or state transition that explains the mismatch. Fix that boundary and rerun the full-fixture and selected-label examples. This creates a stronger explanation than changing several unrelated parts until the screen looks right.

The scenario-specific acceptance check is: Document the all-or-nothing fixture assumption before adding partial returns. Preserve before-and-after evidence. Add a missing project_name, a negative part_count, an unrecognised status and a duplicate record_id as separate invalid cases. Define the rejection or duplicate-handling policy before testing, and verify that invalid input does not silently change valid existing records.

Check the Git and GitHub Workflow concerns as well:

• A fresh checkout must reproduce the exercise.
• The diff must not include secrets or unrelated files.
• A conflict resolution must preserve the intended rule.

For an empty filter match, the expected sum value is 0. Keep matching_count at zero. This distinction prevents an empty dataset from being interpreted as a measured observation.

Explain the finished work in a portfolio

Show the student maker-team lead question, the record definition and the expected calculation first. Then demonstrate a project_name filter and the acceptance check. Include the fixture, setup instructions, chosen tool versions, actual test output and one remaining limitation in the repository. If you show a screenshot, pair it with the input that produced it. Another learner should be able to repeat the same result from a clean checkout.

For a focused extension, add a second project_name selection and compare the two groups using the same rule. Specify how missing groups appear and keep the original fixture as a regression case. Expand scope only after the current calculation, state handling and recovery path remain understandable.

Questions learners often ask

Which part_request records belong in the result?

Select records whose status is exactly issued and that satisfy the chosen project_name filter. Other states remain in the source data and can have separate summaries. Follow the domain rule above when a record changes state.

What should happen when no records match?

Return a zero total with a matching count of zero and a clear empty-result message. Keep the applied filter visible so the user can change it. Avoid using a loading indicator for a completed request that simply has no matching data.

How can I prove the part_count result is correct?

Reconcile the first and third sample records, then repeat the calculation for Sensor Display alone. Save both expected and actual outputs, and rerun the scenario-specific acceptance check after making a change.

Continue learning with Groot Academy

Use this exercise as a concrete discussion point when choosing a learning path. Browse the current Groot Academy course directory and ask about the current syllabus, learning mode and project practice. Course availability and batch details should be confirmed directly with the academy.

For implementation details, consult the official Git and GitHub Workflow documentation matching the tools you install. This project defines an original practice brief; it does not depend on a forecast about 2027 software releases.

Continue with Robotics Practice Runs using Git and GitHub Workflow, or compare Maker Project Parts using Linux Administration. These companion practice guides are part of the 2027 learning collection.