- Added debug statements in `generate-pr-plugin.sh` to display the tarball path, backup directory, and list of files being processed, improving visibility during deployment.
- Updated `pr-plugin-build.yml` to include output of the file list and tarball contents, aiding in verification and troubleshooting during the build process.
- Updated `generate-pr-plugin.sh` to accept an optional plugin URL parameter for improved flexibility.
- Modified the script to generate a default plugin URL if none is provided, ensuring consistent naming conventions.
- Enhanced the GitHub Actions workflow to generate and output stable URLs for both the tarball and plugin files, facilitating easier updates.
- Updated the file extraction method in `generate-pr-plugin.sh` to use a temporary file, improving compatibility and avoiding subshell issues.
- Added cleanup for the temporary file after processing the extracted file list.
- Added error handling and improved variable handling in `generate-pr-plugin.sh`.
- Updated placeholder values in the generated plugin file for clarity.
- Enhanced the UI in `Plugins.page` to indicate that the page is modified for PR testing.
- Updated `generate-pr-plugin.sh` to include a new parameter for TXZ URL and modified usage instructions.
- Enhanced the GitHub Actions workflow to upload the TXZ file to R2 and generate the corresponding public URL.
- Improved installation instructions in the PR comment to provide direct download links for the PLG and TXZ files.
- Modified the sed command in `generate-pr-plugin.sh` to support both Linux and macOS environments.
- Updated the `pr-plugin-build.yml` workflow documentation to include a step for creating the necessary plugin directory.
- Changed the local path for the downloaded tarball to include the 'webgui-pr' directory.
- Updated the cleanup command to remove the correct plugin file based on the new path structure.
- Introduced a new script `generate-pr-plugin.sh` to automate the creation of Unraid PR plugin files.
- Added a GitHub Actions workflow `pr-plugin-build.yml` to build and package the plugin when changes are made to the `emhttp` directory.
- The workflow includes steps for checking out code, generating versioning, creating a tarball, and uploading the plugin artifact for PR testing.
