Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

[Change Requests] - Skip the change request for non-meaningful project edits

Open
#4,424 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description
Context

Right now, editing a project's data requires a Standard change request, even for minor changes. We want only "meaningful" edits, budget, timeline, and deliverables/scope to require a CR. Everything else should just apply directly and still leave an audit trail, so there are no more trivial CRs.

Task

In the project edit path, detect whether only non-meaningful fields changed; if so, apply the edit directly and log a Change row instead of creating/requiring a Standard CR. If any meaningful field changed, keep the same CR behavior.

Acceptance Criteria
  • One named constant defines the "meaningful" fields (budget, timeline, deliverables/scope) in a single place.
  • Editing only non-meaningful fields applies immediately with no Standard CR, and records a Change row.
  • Editing any meaningful field till requires the CR.
  • Leadership changes are unaffected (they already have their own leadership CR path).

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

Start at the project edit path and trace how Standard change requests are currently required and how Change rows are recorded. Identify the existing meaningful project fields and leadership CR path, then verify that non-meaningful-only edits apply directly with an audit row while meaningful edits retain the CR behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.