Skip to content

Conversation

@JereSalo
Copy link
Contributor

@JereSalo JereSalo commented Dec 4, 2025

Motivation

Description

  • Had to change pull_request_target to pull_request because this makes the workflow apply immediately. With pull_request_target the workflow that would've run would've been the main one, which still blocks uppercase characters.

Edit: Had to change the title to lowercase because the old workflow is still running as it was a pull_request_target 😞

Example job run https://github.com/lambdaclass/ethrex/actions/runs/19934067966/job/57153864030?pr=5519

@github-actions github-actions bot added the L1 Ethereum client label Dec 4, 2025
@JereSalo JereSalo marked this pull request as ready for review December 4, 2025 15:21
@JereSalo JereSalo requested a review from a team as a code owner December 4, 2025 15:21
Copilot AI review requested due to automatic review settings December 4, 2025 15:21
@ethrex-project-sync ethrex-project-sync bot moved this to In Review in ethrex_l1 Dec 4, 2025
Copilot finished reviewing on behalf of JereSalo December 4, 2025 15:22
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR removes the restriction that prevented PR titles from starting with uppercase characters. The change enables more natural sentence casing in PR titles while maintaining the semantic commit format requirements.

  • Removed the lowercase-only constraint from PR title validation
  • Updated documentation to reflect the new rule and provide an example with uppercase
  • Changed workflow trigger from pull_request_target to pull_request for immediate application

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
CONTRIBUTING.md Removed the requirement that subjects must not start with uppercase and updated example to demonstrate uppercase usage
.github/workflows/pr_lint_pr_title.yml Commented out the regex pattern enforcing lowercase subjects and changed trigger to pull_request for immediate effect

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@JereSalo JereSalo changed the title chore(l1): ALLOW PR title to begin with UPPERCASE chore(l1): allow PR title to begin with UPPERCASE Dec 4, 2025
Copy link
Contributor

@ElFantasma ElFantasma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

☺️

Copy link
Contributor

@gianbelinche gianbelinche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😲

Copy link
Collaborator

@mpaulucci mpaulucci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still should be a letter A to Z, whether underscore or upperscore

@github-project-automation github-project-automation bot moved this from In Review to In Progress in ethrex_l1 Dec 4, 2025
@JereSalo
Copy link
Contributor Author

JereSalo commented Dec 4, 2025

It still should be a letter A to Z, whether underscore or upperscore

Yeah, I agree.
Note that the previous regex didn't cover this either though. Any title could've started with something like "123 Title" and it would've been accepted anyway because the only restriction it imposed was that the first symbol couldn't be an uppercase letter.

I changed it here, now it can only start with a letter. Thanks for noticing!

@JereSalo JereSalo requested a review from mpaulucci December 4, 2025 16:20

on:
pull_request_target:
pull_request:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did you change this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

L1 Ethereum client

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

5 participants