GitAuto: [FEATURE] Include JSON file in GitHub release files

[gitauto-ai]

Resolves #610

What is the feature

This feature ensures that the JSON file is included in the GitHub release files generated by the pipeline (AppVeyor). Currently, only the NuGet package (.nupkg) is attached to the release, leaving out the necessary JSON file. Including the JSON file will provide additional configuration or metadata required for users.

Where / How to code and why

The appveyor.yml pipeline configuration will be modified to include the JSON file in the list of artifacts for the release. This involves updating the artifacts section to package or copy the JSON file to the appropriate location before the release step. By doing so, both the .nupkg and the JSON files will be attached to the GitHub release, ensuring all necessary files are available to users. This approach follows best practices by maintaining a single source of truth for release artifacts and automating the inclusion of all essential files.

Anything the issuer needs to do

• Update the appveyor.yml configuration to include the JSON file in the artifacts section.
• Ensure the JSON file is correctly placed or generated before the release step in the pipeline.
• Test the pipeline to confirm that both .nupkg and JSON files are attached to the GitHub release.

Test these changes locally

git fetch origin
git checkout gitauto/issue-610-20241226-002457
git pull origin gitauto/issue-610-20241226-002457

Summary by Sourcery

Include the data/bancos.json file in the GitHub release artifacts.

New Features:

• Include the JSON file in the GitHub release files.

Tests:

• Test the pipeline to confirm that both the NuGet package and the JSON file are attached to the GitHub release.

[korbit-ai]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the AppVeyor configuration to include a JSON file in GitHub releases. The change involves adding the data/bancos.json file to the list of artifacts in the appveyor.yml file, ensuring it is included alongside the NuGet package in the release.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Include JSON file in release artifacts	Added data/bancos.json to the artifacts section of the AppVeyor configuration file to include the JSON file in the release artifacts alongside the NuGet package.	appveyor.yml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#610	Include JSON file in GitHub release artifacts by modifying pipeline configuration	✅
#610	Ensure JSON file is properly packaged before release	✅

Possibly linked issues

• [FEATURE] Include JSON file in GitHub release files #610: The PR addresses the issue by adding the JSON file to the artifacts in the appveyor.yml file, ensuring it is included in the GitHub release.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, gitauto-ai[bot]!). We assume it knows what it's doing!

[github-actions]

Summary

Status	Count
🔍 Total	455
✅ Successful	234
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	220
❓ Unknown	0
🚫 Errors	1

Errors per input

Errors in ./data/bancos.md

• [ERROR] https://bancoclassico.com.br/ | Network error: error sending request for url (https://bancoclassico.com.br/) Maybe a certificate error?
  Full Github Actions output

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2:10AM INF scanning for exposed secrets...
2:10AM INF 1076 commits scanned.
2:10AM INF scan completed in 2.63s
2:10AM INF no leaks found

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud