Handling fixes applied by linting

[cfsb-jrose]

Hello,

We currently run linting in Jenkins pipelines. When we enable APPLY_FIXES, I was wondering if megalinter had configuration that would be able to push commit instead of handling independently (e.g. running git commands in the pipeline)?

[nvuillam]

@cfsb-jrose the default Jenkinsfile pipeline doesn't allow that, but I'd be glad to update it if you provide the relevant step :)

Basically, it has to do the same than what is done in the GitHub Action

      - name: Prepare commit
        if: env.APPLY_FIXES_IF_COMMIT == 'true'
        run: sudo chown -Rc $UID .git/

      - name: Commit and push applied linter fixes
        uses: stefanzweifel/git-auto-commit-action@v5
        if: env.APPLY_FIXES_IF_COMMIT == 'true'
        with:
          branch: >-
            ${{
              github.event.pull_request.head.ref ||
              github.head_ref ||
              github.ref
            }}
          commit_message: "[MegaLinter] Apply linters fixes"
          commit_user_name: megalinter-bot
          commit_user_email: 129584137+megalinter-bot@users.noreply.github.com

[cfsb-jrose]

Thank you for sharing, but the question was whether there's interest to have an internal mechanism to push commits for fixes instead of logic in the pipeline?

[nvuillam]

@cfsb-jrose there could be, but we'd have to handle all the specificities of all Git providers... so I prefer it remains in the workflows where we can use actions and recommendations defined by each provider :)

[cfsb-jrose]

We use Jenkins + Bitbucket and found the current solution somewhat clunky. Any recommendations?

[nvuillam]

If you could share your configuration, we could update MegaLinter documentation with it :)

It's not planned to handle commit + git + push directly within MegaLinter core code for all platforms

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.