Add issue template for revdep check failures#7672
Open
Keykyrios wants to merge 2 commits intoRdatatable:masterfrom
Open
Add issue template for revdep check failures#7672Keykyrios wants to merge 2 commits intoRdatatable:masterfrom
Keykyrios wants to merge 2 commits intoRdatatable:masterfrom
Conversation
Add a YAML issue form template (.github/ISSUE_TEMPLATE/revdep_check_failure.yml) for data.table maintainers to report reverse dependency check failures that should be fixed before the next CRAN release. Based on the 'Steps to report a new revdep check problem' section of https://github.com/Rdatatable/data.table/wiki/Revdep-checks The template includes: - pre-filing verification checklist (issue reproducibility, git bisect, etc.) - required fields: affected package, problem description, failing check output, first bad commit/PR link, R version(s) affected - optional fields: minimal reproducible example, additional context - auto-labels issues with 'revdep'
tdhock
requested changes
Mar 17, 2026
Comment on lines
+36
to
+40
| label: Affected package | ||
| description: Name of the revdep package that fails with data.table master. | ||
| placeholder: e.g. mlr3 | ||
| validations: | ||
| required: true |
Comment on lines
+51
to
+52
| revdep shapr has new test failures due to warnings when | ||
| data.table master is installed. |
Member
There was a problem hiding this comment.
Suggested change
| revdep shapr has new test failures due to warnings when | |
| data.table master is installed. | |
| revdep shapr has new test failures. |
Comment on lines
+81
to
+91
| - type: dropdown | ||
| id: r-version | ||
| attributes: | ||
| label: R version(s) affected | ||
| description: Which R version(s) show this failure? | ||
| options: | ||
| - Both R-devel and R-release | ||
| - R-devel only | ||
| - R-release only | ||
| validations: | ||
| required: true |
Comment on lines
+12
to
+31
| - type: checkboxes | ||
| id: verification | ||
| attributes: | ||
| label: Pre-filing verification | ||
| description: | | ||
| Confirm the issue is real per the | ||
| [wiki guidelines](https://github.com/Rdatatable/data.table/wiki/Revdep-checks#steps-to-report-a-new-revdep-check-problem). | ||
| options: | ||
| - label: Found in more than one recent check (e.g. previous day) | ||
| required: false | ||
| - label: Occurs in both R-devel and R-release, or noted which one | ||
| required: false | ||
| - label: Result for data.table release matches result from CRAN | ||
| required: false | ||
| - label: "`git bisect` found a non-trivial first bad commit" | ||
| required: false | ||
| - label: Issue is in master (not only in release) | ||
| required: false | ||
| - label: Searched existing issues for this package and commit/PR | ||
| required: false |
Member
There was a problem hiding this comment.
all these should be true before posting, please delete
| value: | | ||
| Use this template to report a new revdep check failure found via | ||
| [revdep checks](https://github.com/Rdatatable/data.table/wiki/Revdep-checks). | ||
| Please verify the failure is real before filing; see checklist below. |
Member
There was a problem hiding this comment.
Suggested change
| Please verify the failure is real before filing; see checklist below. | |
| Please verify the failure is real before filing; see checklist on that page. |
Member
|
also can you please enable issues on your fork so we can preview what this would look like? |
Author
|
@tdhock I have made your requested changes, as well as enabled the issues on my fork! |
Member
|
ok it looks like this Keykyrios#1 |
Member
|
I think the problem description and MRE fields should be deleted, and change additional context prompt to indicate that MRE can be included there. |
Member
|
also can you please automatically assign the revdep label? |
Member
|
here are previous issues |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #7658.
Adds a YAML issue form template (.github/ISSUE_TEMPLATE/revdep_check_failure.yml)
for data.table maintainers to report revdep check failures that should be fixed
before the next CRAN release.
Based on the "Steps to report a new revdep check problem" section of the
Revdep checks wiki
(not the revdep issue template wiki, which is for issues in other repos).
The template includes:
revdep