Skip to content

Ban TODO comments, require FIXME comments #2511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 25, 2025

Conversation

joshlf
Copy link
Member

@joshlf joshlf commented Apr 25, 2025

This allows us to leave TODO comments for things that should be resolved
before a PR is merged, and have stronger guarantees that these will
actually be resolved. Previously, we've manually created GitHub PR
review comments for TODO comments, which has let some TODOs through by
accident, and is generally a waste of developer time.


This PR is on branch ban-todo.

This allows us to leave TODO comments for things that should be resolved
before a PR is merged, and have stronger guarantees that these will
actually be resolved. Previously, we've manually created GitHub PR
review comments for TODO comments, which has let some TODOs through by
accident, and is generally a waste of developer time.

gherrit-pr-id: I4b767eb773d725fce0abefbefbe74c24a4b56d90
@joshlf joshlf enabled auto-merge April 25, 2025 16:07
@joshlf joshlf requested a review from jswrenn April 25, 2025 16:07
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.37%. Comparing base (1fea6a1) to head (87e9563).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2511   +/-   ##
=======================================
  Coverage   90.36%   90.37%           
=======================================
  Files          19       19           
  Lines        7808     7809    +1     
=======================================
+ Hits         7056     7057    +1     
  Misses        752      752           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines +25 to +28
echo "Found $KEYWORD markers in the codebase." >&2
echo "$KEYWORD is used for tasks that should be done before merging a PR; if you want to leave a message in the codebase, use FIXME." >&2
echo "" >&2
echo "$output" >&2
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Though perhaps use ::notice, to be a bit less visually disruptive.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe let's follow up in a separate PR so we can do that to all of our CI scripts at once? We'll also need to figure out how to make the output nice when run from a git pre-push hook.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good.

@joshlf joshlf added this pull request to the merge queue Apr 25, 2025
Merged via the queue into main with commit 1f929d2 Apr 25, 2025
89 checks passed
@joshlf joshlf deleted the I4b767eb773d725fce0abefbefbe74c24a4b56d90 branch April 25, 2025 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants