Correct sync list, add issue repo and version info

[gridhead]

Signed-off-by: Akashdeep Dhar akashdeep.dhar@gmail.com

[codecov-commenter]

Codecov Report

Merging #263 (4d262c7) into develop (6869c27) will not change coverage.
The diff coverage is n/a.

❗ Current head 4d262c7 differs from pull request most recent head bc00f68. Consider uploading reports for the commit bc00f68 to get more accurate results

@@           Coverage Diff            @@
##           develop     #263   +/-   ##
========================================
  Coverage    88.41%   88.41%           
========================================
  Files           14       14           
  Lines         1174     1174           
  Branches       172      172           
========================================
  Hits          1038     1038           
  Misses         123      123           
  Partials        13       13           

Flag	Coverage Δ
unittests	88.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6869c27...bc00f68. Read the comment docs.

[gridhead]

Assuming it didn't find git (ref. https://github.com/fedora-infra/fedora-messaging/runs/6452182270?check_suite_focus=true#step:4:12), I added a directive to explicitly install it (ref. https://github.com/fedora-infra/fedora-messaging/pull/263/files#diff-ef2cef9f88b4fe09ca3082140e67f5ad34fb65fb6e228f119d3812261ae51449R31). Let us see if it works.

[gridhead]

Hmm. This is strange. I have git installed and I can confirm that I am in the correct directory (ref. https://github.com/fedora-infra/fedora-messaging/runs/6463365423?check_suite_focus=true). It still does not seem to work.

[gridhead]

This is where I took reference from pre-commit/pre-commit#456. I will go out there and take a walk before I have at this (again).

[abompard]

Did you have a look at the pre-commit error log? I suspect it may be related to the git safe-directory feature I fixed in FASJSON: fedora-infra/fasjson@8f13c92.
I'll see if I can apply the same fix here.

[gridhead]

I tried to add a task to cat the logs after the job failed but then I remember that nothing really executes once a command exits out with a non-zero exit code. So it didn't quite work.

[abompard]

Well, it's more complex than I thought, so it'll have to wait for tomorrow if you don't mind (I'm supposed to be off today ;-) ).

[gridhead]

@abompard, apologies. I am totally okay with waiting on this. I will probably bang my head on Noggin in the meanwhile. :P

[abompard]

Alright, please rebase, it should pass now.