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

Add alt text #43

Merged
merged 1 commit into from
Dec 19, 2024
Merged

Add alt text #43

merged 1 commit into from
Dec 19, 2024

Conversation

beckykd
Copy link
Contributor

@beckykd beckykd commented Dec 18, 2024

Alt text is required for image accessibility.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 12399707125

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 12361162701: 0.0%
Covered Lines: 577
Relevant Lines: 577

💛 - Coveralls

Copy link
Member

@mrossinek mrossinek left a comment

Choose a reason for hiding this comment

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

In principal I approve, I am just confused why the docs CI job started to fail.
Sending a PR to fix this now

@mrossinek mrossinek added the stable backport potential Label for mergify to open a backport PR label Dec 19, 2024
@mrossinek mrossinek merged commit ed55040 into Qiskit:main Dec 19, 2024
14 of 15 checks passed
mergify bot pushed a commit that referenced this pull request Dec 19, 2024
(cherry picked from commit ed55040)
@mergify mergify bot mentioned this pull request Dec 19, 2024
mrossinek pushed a commit that referenced this pull request Dec 19, 2024
(cherry picked from commit ed55040)

Co-authored-by: Rebecca Dimock <66339736+beckykd@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stable backport potential Label for mergify to open a backport PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants