✨ PR Lint - ensure title is not a default one

Open
#2,587 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs
Domain
ci-cd, tooling

Research direction

Start by locating the existing PR Linter entry point in the SSW.Website repository and review how it validates pull request titles. Check the TinaCMS default titles mentioned in the issue, then confirm that those titles are rejected while descriptive titles pass.

Written by the indexing model from the issue text.

Description

There have been a lot of commits to main on the website repo with the commit message: "TinaCMS content update" or "Update from TinaCMS".

Today, I was trying to sort through a bug and had to drill into the PR changes to work out if a particular commit was contributing to the issue - this was harder than it should've been since the commit messages were based off the PR titles, and these were default/generic messages.

Image

### Tasks
- [ ] PR Linter - update to check that PR titles are not Tina default ones
Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

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.

More from SSWConsulting/SSW.Website

All issues in SSWConsulting/SSW.Website

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.