Issue sending hacking challenge commit

What happens

I uploaded a hacking challenge solution with commit and pushed it from my local branch to the remote challenge repository, but auto-running the jobs from the remote repository shows me that the build runs failed and there are several errors.

What do you understand or find about that problem

I think it doesn’t recognize my username and email modification in the .mailmap file
and other issues like .feature and .templates. yaml files with incorrect formats

Did you try any workaround? What did you do?

I didn’t really do anything, because according to me, the files were modified correctly.

(Optional) Why does the workaround fail?

I didn’t succeed because I don’t know how to approach the problem.

Evidences


links:
/lintGitMailMap: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502372

/test/policy: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502430

/solutions/gherkin/hack: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502369

/test/generic/80_columns: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502388

/test/commit_msg: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502387

/test/generic/no_tabs: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502397

/test/generic/check_date: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502403

/test/generic/check_files:
https://gitlab.com/autonomicjump/challenges/-/jobs/6157502404

/test/others/10_external_links: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502412

/test/generic/user_yaml/checks: https://gitlab.com/autonomicjump/challenges/-/jobs/6157502411

I need help with

the solution or solutions to solve those failed job problems.

Hello, you should try to solve the errors you have according to the Pipelines alerts. For example, your branch is 96 changes out of date, you must update it.

What do you mean by “your branch is 96 changes out of date, you must update it.” I don’t understand, Can you be more explicit please?

Sure! Look, what happens is that the branch has 101 changes that have not been updated. You can update it and then try to fix the other pipelines.

and by updating them do you mean running a git pull command on my local repository or am I wrong?

Yeah! The idea is that it is always updated. After that, you can try to resolve the pipelines that come out.