Skip to content
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

Links with identical accessible names and same context serve equivalent purpose" [fd3a94]: Reduced images size for failed examples [4,8] #2178

Conversation

giacomo-petri
Copy link
Collaborator

Closes #2177

Updated images size for failed examples 4,5,6,7, and 8.

This can be merged with 1 approval: editorial changes to test code


Pull Request Etiquette

When creating PR:

  • Make sure you're requesting to pull a branch (right side) to the develop branch (left side).
  • Make sure you do not remove the "How to Review and Approve" section in your pull request description

After creating PR:

  • Add yourself (and co-authors) as "Assignees" for PR.
  • Add label to indicate if it's a Rule, Definition or Chore.
  • Link the PR to any issue it solves. This will be done automatically by referencing the issue at the top of this comment in the indicated place.
  • Optionally request feedback from anyone in particular by assigning them as "Reviewers".

When merging a PR:

  • Close any issue that the PR resolves. This will happen automatically upon merging if the PR was correctly linked to the issue, e.g. by referencing the issue at the top of this comment.

How to Review And Approve

  • Go to the “Files changed” tab
  • Here you will have the option to leave comments on different lines.
  • Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
  • Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.

@giacomo-petri giacomo-petri added the Editorial For editorial changes that does not change the meaning of a rule or Glossary term label Apr 10, 2024
@giacomo-petri giacomo-petri requested a review from Jym77 April 10, 2024 12:35
@giacomo-petri giacomo-petri self-assigned this Apr 10, 2024
Copy link
Member

@WilcoFiers WilcoFiers left a comment

Choose a reason for hiding this comment

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

Minor tweak

…and-context-serve-equivalent-purpose-images-size-fix
…and-context-serve-equivalent-purpose-images-size-fix
@carlosapaduarte carlosapaduarte merged commit d9a44b4 into develop Aug 1, 2024
2 checks passed
@carlosapaduarte carlosapaduarte deleted the giacomo-petri-links-with-identical-names-and-context-serve-equivalent-purpose-images-size-fix branch August 1, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Editorial For editorial changes that does not change the meaning of a rule or Glossary term reviewers wanted
Projects
None yet
4 participants