You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently trying to contribute to the maintenance of manifest files in a Scoop bucket. I have been manually updating the manifest files locally and creating pull requests (PRs) for my changes. Specifically, I have been modifying the checkver section, including the url and regex fields. However, I am unsure if my approach is correct and efficient.
Here are my main questions and concerns:
Manual Updates: I have been manually changing the version field, the URLs, and the hash values in the architecture section of the manifest. This process feels cumbersome and prone to errors. Is this the intended workflow for maintaining manifest files?
Automation with checkver: I understand that the checkver section helps in automatically checking for new versions. Should I be focusing only on updating the checkver section? Will the other fields like version, architecture.url, and architecture.hash be automatically updated by a workflow or automation tool once checkver is correctly configured?
Best Practices: Could you please provide some guidance or best practices for maintaining manifest files in a Scoop bucket? Any tips on how to streamline the process and ensure accuracy would be greatly appreciated.
Here is an example of a manifest file I recently updated: origin
I would greatly appreciate any advice or instructions on how to proceed effectively with maintaining the manifest files. Thank you for your assistance!
The text was updated successfully, but these errors were encountered:
Your focus should be on ensuring the accuracy of the checkver and download links, as the updates will be handled automatically by the GitHub Action Bot, Manually update is not recommend. As you've noticed, most commits in this repository are made by the GitHub Action Bot.
Check for official wiki to find guidance, and others manifest is best practices.
Hello,
I am currently trying to contribute to the maintenance of manifest files in a Scoop bucket. I have been manually updating the manifest files locally and creating pull requests (PRs) for my changes. Specifically, I have been modifying the
checkver
section, including theurl
andregex
fields. However, I am unsure if my approach is correct and efficient.Here are my main questions and concerns:
Manual Updates: I have been manually changing the
version
field, the URLs, and the hash values in thearchitecture
section of the manifest. This process feels cumbersome and prone to errors. Is this the intended workflow for maintaining manifest files?Automation with
checkver
: I understand that thecheckver
section helps in automatically checking for new versions. Should I be focusing only on updating thecheckver
section? Will the other fields likeversion
,architecture.url
, andarchitecture.hash
be automatically updated by a workflow or automation tool oncecheckver
is correctly configured?Best Practices: Could you please provide some guidance or best practices for maintaining manifest files in a Scoop bucket? Any tips on how to streamline the process and ensure accuracy would be greatly appreciated.
Here is an example of a manifest file I recently updated:
origin
after
I would greatly appreciate any advice or instructions on how to proceed effectively with maintaining the manifest files. Thank you for your assistance!
The text was updated successfully, but these errors were encountered: