Skip to content

Linting errors to be addressed #32

Closed

Description

@hdamker

The centralized linting update revealed several linting errors with the current repository content. They should be addressed before continuing the content work.

@FabrizioMoggio Do you plan to create an issue for the Gherkin linting issues? Would at least make sense to address them before the next feature PR to avoid getting disturbed by the failed check.

@hdamker got it. Yes I will address the linting errors

Originally posted by @FabrizioMoggio in #29 (comment)

Activity

  1. FabrizioMoggio commented on Oct 29, 2025

    @FabrizioMoggio
    Contributor

    @hdamker I have addressed the linting error with: #33

    Anyway #31 still refers to the old Repo image I suppose. I tried to re-run the linting tool on #31 but the error are still there even if the problems have been addressed in Main.

  2. hdamker commented on Oct 29, 2025

    @hdamker
    ContributorAuthor

    Anyway #31 still refers to the old Repo image I suppose. I tried to re-run the linting tool on #31 but the error are still there even if the problems have been addressed in Main.

    @FabrizioMoggio yes, the PR #31 branch (rkandoi:main) was most probably forked from camaraproject:main before PR #33 was merged. For PR #31 the check is not relevant and can be merged as is. To get the check there green the PR author would need to sync the PR with main, but as said: not relevant. Just ensure that any new PR will be only merged when the check is green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions