Skip to content

Add Priority to README #296

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

ToddBradley
Copy link

@ToddBradley ToddBradley commented May 25, 2025

This adds a little Priority section to the README, in response to issue #295.

Fixes #295.

@icemac icemac requested a review from Copilot June 17, 2025 07:02
Copy link

@Copilot 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 adds a new "Priority" section to the README to explain the precedence of rerun failure configurations, addressing issue #295.

  • Introduces a dedicated section to describe the order of priority for specifying rerun counts
  • Uses start/end markers (START-PRIORITY/END-PRIORITY) to clearly encapsulate the new documentation block
Comments suppressed due to low confidence (1)

README.rst:238

  • [nitpick] Consider rephrasing this sentence to improve clarity. For example, you might explicitly state the hierarchy of configuration precedence to enhance readability.
You can specify arguments in three places. So if you set the number of reruns in all three, 

@icemac icemac enabled auto-merge (squash) June 17, 2025 07:03
@icemac
Copy link
Contributor

icemac commented Jun 17, 2025

Thank you for this PR.

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.

documentation should clarify priority of configuration
2 participants