Add logging to project automations

[Proibito04]

Fixes

Fixes #3396 by @dhruvkb

Description

This pull request adds detailed console.log statements for improved debugging in issues.mjs and prs.mjs, enhancing visibility in GitHub Actions workflows.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

@Proibito04 from a cursory reading, it seems great work, thank you for the contribution! I do have a few notes.

• The Lint check is failing, which indicates that your code diverges from the style guide. You can examine the output of the Lint check to determine what needs to be fixed.
• Debug logs are not visible in the GitHub UI unless the action is being re-run with debug level logging. Thus you should make some progress tracking logs higher level than debug so that they always show up.
• Since we are running these workflows inside actions/github-script, we can use the @actions/core package (can be passed as an arg to the main function) to write logs that will automatically handle the relevant ::_:: prefix.
• Some of the logs that are often repeated adjacent to a function or util can be moved into that function or util class itself. That will significant DRY up the code changes.

[Proibito04]

@dhruvkb, thank you for your suggestions. I've removed the imports and passed core through the function parameters. I've also streamlined the code by moving numerous debug statements into moveCard

[dhruvkb]

This is a huge improvement, and thanks for constantly iterating on feedback! I want to emphasise that this is incredible as it is and we're only iterating on nit picks and minor implementation details now.

But as always, there is scope for more refinement. I've listed down some ideas as comments below. I hope you don't mind more iterations but if you do, please let us know and we'll be happy to apply the finishing touches and merge it.

I also made some changes to your code as an example with explanations below each change. If you could apply them in other areas, that would be awesome.

[openverse-bot]

Based on the low urgency of this PR, the following reviewers are being gently reminded to review this PR:

@obulat
@sarayourfriend
This reminder is being automatically generated due to the urgency configuration.

Excluding weekend¹ days, this PR was ready for review 5 day(s) ago. PRs labelled with low urgency are expected to be reviewed within 5 weekday(s)².

@Proibito04, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings.

Footnotes

1. Specifically, Saturday and Sunday. ↩

2. For the purpose of these reminders we treat Monday - Friday as weekdays. Please note that the operation that generates these reminders runs at midnight UTC on Monday - Friday. This means that depending on your timezone, you may be pinged outside of the expected range. ↩

[obulat]

Thank you for your contribution, @Proibito04, great work!