Skip to content

[Bugfix:Developer] Fix CI Status in README#12634

Merged
williamjallen merged 2 commits into
mainfrom
fix-ci-read-me
Mar 23, 2026
Merged

[Bugfix:Developer] Fix CI Status in README#12634
williamjallen merged 2 commits into
mainfrom
fix-ci-read-me

Conversation

@JManion32

Copy link
Copy Markdown
Contributor

Why is this Change Important & Necessary?

The README.md file for the Submitty repository includes a status indicator for CI. I noticed that the status consistently is no status.
image

What is the New Behavior?

Changed this line to look for ci.yml instead of submitty_ci.yml:

[![CI](https://github.com/Submitty/Submitty/actions/workflows/ci.yml/badge.svg?event=push)](https://github.com/Submitty/Submitty/actions/workflows/ci.yml)

Now, the status of CI is passing:
image

What steps should a reviewer take to reproduce or test the bug or new feature?

To replicate, I made a fork of the Submitty repository, and observed the no status status. I then changed the README.md to look for ci.yml instead of submitty_ci.yml, and the status became passing.

Automated Testing & Documentation

N / A

Other information

N / A

@codecov

codecov Bot commented Mar 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 21.66%. Comparing base (8497aa3) to head (4609557).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##               main   #12634   +/-   ##
=========================================
  Coverage     21.66%   21.66%           
  Complexity     9639     9639           
=========================================
  Files           268      268           
  Lines         36226    36226           
  Branches        487      487           
=========================================
  Hits           7847     7847           
  Misses        27896    27896           
  Partials        483      483           
Flag Coverage Δ
autograder 21.32% <ø> (ø)
js 2.04% <ø> (ø)
migrator 100.00% <ø> (ø)
php 20.68% <ø> (ø)
python_submitty_utils 80.08% <ø> (ø)
submitty_daemon_jobs 91.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@IDzyre IDzyre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Works on my fork as well.

@github-project-automation github-project-automation Bot moved this from Seeking Reviewer to Awaiting Maintainer Review in Submitty Development Mar 23, 2026
@williamjallen
williamjallen merged commit f740e33 into main Mar 23, 2026
27 checks passed
@williamjallen
williamjallen deleted the fix-ci-read-me branch March 23, 2026 22:59
@github-project-automation github-project-automation Bot moved this from Awaiting Maintainer Review to Done in Submitty Development Mar 23, 2026
GarvitKhandelwal31 pushed a commit to GarvitKhandelwal31/Submitty that referenced this pull request Mar 25, 2026
### Why is this Change Important & Necessary?
The `README.md` file for the Submitty repository includes a status
indicator for CI. I noticed that the status consistently is `no status`.
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/1ba43986-8e7b-43ad-bbd0-d592a5f159a5"
/>

### What is the New Behavior?
Changed this line to look for `ci.yml` instead of `submitty_ci.yml`:
```
[![CI](https://github.com/Submitty/Submitty/actions/workflows/ci.yml/badge.svg?event=push)](https://github.com/Submitty/Submitty/actions/workflows/ci.yml)
```
Now, the status of CI is `passing`:
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/d5add559-4200-4360-ba72-f0c09b893e79"
/>

### What steps should a reviewer take to reproduce or test the bug or
new feature?
To replicate, I made a fork of the Submitty repository, and observed the
`no status` status. I then changed the `README.md` to look for `ci.yml`
instead of `submitty_ci.yml`, and the status became `passing`.

### Automated Testing & Documentation
N / A

### Other information
N / A
GarvitKhandelwal31 pushed a commit to GarvitKhandelwal31/Submitty that referenced this pull request Mar 29, 2026
### Why is this Change Important & Necessary?
The `README.md` file for the Submitty repository includes a status
indicator for CI. I noticed that the status consistently is `no status`.
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/1ba43986-8e7b-43ad-bbd0-d592a5f159a5"
/>

### What is the New Behavior?
Changed this line to look for `ci.yml` instead of `submitty_ci.yml`:
```
[![CI](https://github.com/Submitty/Submitty/actions/workflows/ci.yml/badge.svg?event=push)](https://github.com/Submitty/Submitty/actions/workflows/ci.yml)
```
Now, the status of CI is `passing`:
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/d5add559-4200-4360-ba72-f0c09b893e79"
/>

### What steps should a reviewer take to reproduce or test the bug or
new feature?
To replicate, I made a fork of the Submitty repository, and observed the
`no status` status. I then changed the `README.md` to look for `ci.yml`
instead of `submitty_ci.yml`, and the status became `passing`.

### Automated Testing & Documentation
N / A

### Other information
N / A
GarvitKhandelwal31 pushed a commit to GarvitKhandelwal31/Submitty that referenced this pull request Apr 14, 2026
### Why is this Change Important & Necessary?
The `README.md` file for the Submitty repository includes a status
indicator for CI. I noticed that the status consistently is `no status`.
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/1ba43986-8e7b-43ad-bbd0-d592a5f159a5"
/>

### What is the New Behavior?
Changed this line to look for `ci.yml` instead of `submitty_ci.yml`:
```
[![CI](https://github.com/Submitty/Submitty/actions/workflows/ci.yml/badge.svg?event=push)](https://github.com/Submitty/Submitty/actions/workflows/ci.yml)
```
Now, the status of CI is `passing`:
<img width="896" height="166" alt="image"
src="https://github.com/user-attachments/assets/d5add559-4200-4360-ba72-f0c09b893e79"
/>

### What steps should a reviewer take to reproduce or test the bug or
new feature?
To replicate, I made a fork of the Submitty repository, and observed the
`no status` status. I then changed the `README.md` to look for `ci.yml`
instead of `submitty_ci.yml`, and the status became `passing`.

### Automated Testing & Documentation
N / A

### Other information
N / A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants