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

GitHub Actions: Change Linter version to @v4 when source code bug is fixed #2479

Closed
2 tasks done
macho-catt opened this issue Nov 14, 2021 · 4 comments · Fixed by #3674
Closed
2 tasks done

GitHub Actions: Change Linter version to @v4 when source code bug is fixed #2479

macho-catt opened this issue Nov 14, 2021 · 4 comments · Fixed by #3674
Assignees
Labels
Bug Something isn't working Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review

Comments

@macho-catt
Copy link
Member

macho-catt commented Nov 14, 2021

Dependency

Source code fix on https://github.com/github/super-linter/issues/2128

Overview

We have to update the version for our linter when the source code bug is fixed to ensure that everything is up to date.

Details

There is a bug with super linter v4.8.3 (the latest version) where the image for the release is missing. Because of this, all GitHub actions related to linting will fail. There is an open issue in the repository of the source code:
https://github.com/github/super-linter/issues/2128

I temporarily updated the version number to v4.8.1 where everything is still working

Action Items

  • Once the bug is fixed in the linked issue above, revert the version number back in line 22 to:
        uses: github/super-linter@v4
  • Confirm the linter works after the change

Resources/Instructions

Issue opened on the source code of the repo: https://github.com/github/super-linter/issues/2128
lint-scss.yml

@macho-catt macho-catt added role: back end/devOps Tasks for back-end developers Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Complexity: Small Take this type of issues after the successful merge of your second good first issue Ready for Prioritization labels Nov 14, 2021
@github-actions
Copy link

Hi @macho-catt.

Good job adding the required labels to this issue.

Additional Resources:
Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done)
Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

@macho-catt macho-catt added the Dependency An issue is blocking the completion or starting of another issue label Nov 14, 2021
@ExperimentsInHonesty ExperimentsInHonesty added Bug Something isn't working and removed Dependency An issue is blocking the completion or starting of another issue labels Nov 22, 2021
@SAUMILDHANKAR SAUMILDHANKAR added the size: 1pt Can be done in 4-6 hours label Jun 18, 2022
@hackforla hackforla deleted a comment from github-actions bot Jul 31, 2022
@attali-david attali-david self-assigned this Sep 2, 2022
@github-actions
Copy link

github-actions bot commented Sep 2, 2022

Hi @attali-david, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@attali-david attali-david removed their assignment Sep 2, 2022
@esantiano esantiano self-assigned this Oct 23, 2022
@github-actions
Copy link

Hi @esantiano, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@esantiano
Copy link
Member

Availability for this week: 2 PM- 4PM
My estimated ETA for completing this issue: 10/25/22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Status: Updated No blockers and update is ready for review
Projects
Development

Successfully merging a pull request may close this issue.

6 participants