GitLab CI: Fix phpcs, eslint, and cspell tests

Created on 31 May 2024, 7 months ago
Updated 27 June 2024, 6 months ago

Problem/Motivation

There are various issues shown in the validation stage of the gitlab pipeline:

https://git.drupalcode.org/project/flood_control/-/pipelines

phpcs, phpstan and more

📌 Task
Status

Fixed

Version

2.3

Component

Code

Created by

🇳🇱Netherlands batigolix Utrecht

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @batigolix
  • Merge request !50[#3451535] Fix pipeline validation chacks → (Merged) created by batigolix
  • First commit to issue fork.
  • Pipeline finished with Failed
    7 months ago
    Total: 214s
    #187137
  • Pipeline finished with Failed
    7 months ago
    Total: 228s
    #187151
  • Pipeline finished with Failed
    7 months ago
    Total: 221s
    #187158
  • Status changed to Needs work 7 months ago
  • Pipeline finished with Failed
    7 months ago
    Total: 221s
    #187251
  • 🇯🇵Japan ptmkenny

    Changing the issue title back because this MR fixes phpcs, eslint, and cspell tests but not phpstan. Phpstan should be handled in a separate issue.

  • Status changed to Needs review 7 months ago
  • 🇮🇳India diwakar07

    Moving to Needs review, since phpcs, eslint, and cspell have been fixed in the MR.
    Please review.

  • Status changed to RTBC 7 months ago
  • 🇯🇵Japan ptmkenny

    These changes look good to me and have consistent formatting. Moving to RTBC.

    One additional change to be considered by the maintainer:

    Since the phpcs, eslint, and cspell tests are now passing, they can be required so that future MRs do not break them (by default, GitLab CI only requires the phpunit tests to pass).

    You can do that by adding the following to .gitlab-ci.yml:

    # Require all tests to pass.
    cspell:
      allow_failure: false
    eslint:
      allow_failure: false
    phpcs:
      allow_failure: false
    
  • Status changed to Needs work 7 months ago
  • 🇳🇱Netherlands batigolix Utrecht

    @ptmkenny : yes, that requirement would be great. So this should be added

    It is OK to ignore phpstan for the moment. I ll make a new issue for that

  • Status changed to Needs review 7 months ago
  • 🇯🇵Japan ptmkenny

    @batigolix Ok, added!

  • Pipeline finished with Failed
    7 months ago
    Total: 201s
    #189621
  • Pipeline finished with Skipped
    7 months ago
    #189760
    • batigolix committed 3b567ed8 on 2.3.x
      Issue #3451535: GitLab CI: Fix phpcs, eslint, and cspell tests
      
    • 6b8a7876 committed on 2.3.x
      Issue #3451535 by Diwakar07, batigolix, ptmkenny: GitLab CI: Fix phpcs,...
    • batigolix authored cec02bbf on 2.3.x
      Issue #3451535: GitLab CI: Fix phpcs, eslint, and cspell tests
      
  • Status changed to Fixed 7 months ago
  • 🇳🇱Netherlands batigolix Utrecht
  • 🇮🇳India diwakar07

    Hi, @batigolix
    Thanks for the update and for closing this issue.
    However, I noticed that there was no credit given for resolving this issue.
    Is there something we are missing?

  • 🇳🇱Netherlands batigolix Utrecht

    Correct, when merging I did not check the authors. I followed up with a commit for the credits. Is that Okay for you?

  • 🇮🇳India diwakar07

    Hi @batigolix,
    Thanks for the update.
    But I still do not see any credit towards my name for this issue.

  • 🇦🇺Australia elc

    Credit as displayed on the d.o website in user profiles & org stats is set by the maintainer when posting to the issue.

    See "Credit & committing" header below where it currently states "A maintainer has not commented and given credit yet.".

    A maintainer needs to tick the appropriate boxes, and/or manually add users who are not listed in the list but who contributed, and then submit a comment.

    Details instructions are available from the link in "Learn more about granting credit. "

    This step has been missed on most recent issues.

  • 🇳🇱Netherlands batigolix Utrecht

    Yes, I agree. I missed this because I use the merge request option in the issue form.
    It is more obvious to copy the correct commit message when you. do the commits on your local machine.

    Apologies for this and I will try to credit you in the upcoming issues.

  • Automatically closed - issue fixed for 2 weeks with no activity.

  • 🇳🇱Netherlands batigolix Utrecht

    Crediting the people that helped out. Thanks

  • 🇮🇳India diwakar07

    Hi @batigolix,

    I understood the fact that you missed the crediting step.
    I later got to learn that it is up to the maintainer to decide whether to credit people or not for working on an issue.

    Appreciate the time you spent going back and crediting people for their work on this issue.
    Hope my work on this issue was helpful, and I did not trouble much with the credit comments.

    Received the credit for the issue.

    Thanks,
    Diwakar.

Production build 0.71.5 2024