dev  

Messages by Thread

• • Re: [I] Ensure that a release can only be deleted or archived, and that the state is clear (tooling-trusted-releases) via GitHub
• [I] Ensure that error messages from the storage interface are informative (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that error messages from the storage interface are informative (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that error messages from the storage interface are informative (tooling-trusted-releases) via GitHub
• [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
  • Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
  • Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
  • Re: [I] /api/project/releases/{name} should return 404 for non-existent project (tooling-trusted-releases) via GitHub
• [I] Consider allowing different authentication methods on a single endpoint (tooling-trusted-releases) via GitHub
  • Re: [I] Consider allowing different authentication methods on a single endpoint (tooling-trusted-releases) via GitHub
  • Re: [I] Consider allowing different authentication methods on a single endpoint (tooling-trusted-releases) via GitHub
  • Re: [I] Allow different authentication methods on a single endpoint (tooling-trusted-releases) via GitHub
  • Re: [I] Allow different authentication methods on a single endpoint (tooling-trusted-releases) via GitHub
• Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR secrets with Puppet (tooling-trusted-releases) via GitHub
• Re: [I] Speed up building the OCI container (tooling-trusted-releases) via GitHub
  • Re: [I] Speed up building the OCI container (tooling-trusted-releases) via GitHub
• [I] @openrefactoryinc.1925 (tooling-trusted-releases) via GitHub
  • Re: [I] @openrefactoryinc.1925 (tooling-trusted-releases) via GitHub
• [I] Make the vast majority of files compatible with `fix_order.sh`, and add to linting (tooling-trusted-releases) via GitHub
  • Re: [I] Make the vast majority of files compatible with `fix_order.sh`, and add to linting (tooling-trusted-releases) via GitHub
  • Re: [I] Make the vast majority of files compatible with `fix_order.sh`, and add to linting (tooling-trusted-releases) via GitHub
• [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • [GH] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • [GH] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • Re: [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • [GH] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • [GH] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • Re: [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • Re: [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • Re: [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
  • Re: [PR] Work to enable automatic distributions (tooling-trusted-releases) via GitHub
• [I] .dockerignore should use allowlist strategy (tooling-trusted-releases) via GitHub
  • Re: [I] .dockerignore should use allowlist strategy (tooling-trusted-releases) via GitHub
  • Re: [I] .dockerignore should use allowlist strategy (tooling-trusted-releases) via GitHub
• [I] Protect the project from low quality PR contributions (tooling-trusted-releases) via GitHub
  • Re: [I] Protect the project from low quality PR contributions (tooling-trusted-releases) via GitHub
  • Re: [I] Protect the project from low quality PR contributions (tooling-trusted-releases) via GitHub
• [I] Integrate ATR with projects vm (tooling-trusted-releases) via GitHub
  • Re: [I] Integrate ATR with projects vm (tooling-trusted-releases) via GitHub
• [I] Reporter integration with BAT (tooling-trusted-releases) via GitHub
  • Re: [I] Reporter integration with BAT (tooling-trusted-releases) via GitHub
  • Re: [I] Reporter integration with BAT (tooling-trusted-releases) via GitHub
  • Re: [I] Reporter integration with BAT (tooling-trusted-releases) via GitHub
• [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
  • Re: [I] Setup projects vm for development (tooling-trusted-releases) via GitHub
• [I] Projects VM track (tooling-trusted-releases) via GitHub
• [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
  • Re: [I] Add easier methods to prevent check results from being cached (tooling-trusted-releases) via GitHub
• [PR] Doc tweaks (tooling-trusted-releases) via GitHub
  • Re: [PR] Doc tweaks (tooling-trusted-releases) via GitHub
  • Re: [PR] Doc tweaks (tooling-trusted-releases) via GitHub
• [PR] New year (tooling-trusted-releases) via GitHub
  • [GH] New year (tooling-trusted-releases) via GitHub
  • [GH] New year (tooling-trusted-releases) via GitHub
  • Re: [PR] New year (tooling-trusted-releases) via GitHub
  • Re: [PR] New year (tooling-trusted-releases) via GitHub
• [I] Remove the Ubuntu Docker container (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the Ubuntu Docker container (tooling-trusted-releases) via GitHub
  • Re: [I] Remove the Ubuntu Docker container (tooling-trusted-releases) via GitHub
• [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
  • Re: [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
  • Re: [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
  • Re: [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
  • Re: [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
  • Re: [I] analyze.yml pre-commit hook now always fails (tooling-trusted-releases) via GitHub
• [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
  • Re: [I] PR labeler fails with permission issue (tooling-trusted-releases) via GitHub
• [PR] Initial stab at documenting Docker (tooling-trusted-releases) via GitHub
  • Re: [PR] Initial stab at documenting Docker (tooling-trusted-releases) via GitHub
  • Re: [PR] Initial stab at documenting Docker (tooling-trusted-releases) via GitHub
  • Re: [PR] Initial stab at documenting Docker (tooling-trusted-releases) via GitHub
• [I] `Multiple rows were found when one or none was required` when uploading a release via `upload-to-atr` (tooling-trusted-releases) via GitHub
  • Re: [I] `Multiple rows were found when one or none was required` when uploading a release via `upload-to-atr` (tooling-trusted-releases) via GitHub
  • Re: [I] `Multiple rows were found when one or none was required` when uploading a release via `upload-to-atr` (tooling-trusted-releases) via GitHub
  • Re: [I] `Multiple rows were found when one or none was required` when uploading a release via `upload-to-atr` (tooling-trusted-releases) via GitHub
  • Re: [I] `Multiple rows were found when one or none was required` when uploading a release via `upload-to-atr` (tooling-trusted-releases) via GitHub
• [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
  • Re: [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
  • Re: [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
  • Re: [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
  • Re: [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
  • Re: [I] Improve documentation for external contributors (tooling-trusted-releases) via GitHub
• [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
  • Re: [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
  • Re: [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
  • Re: [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
  • Re: [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
  • Re: [I] Need some docs on how to use Docker for testing (tooling-trusted-releases) via GitHub
• [I] Port should be 8080 (tooling-trusted-releases) via GitHub
  • Re: [I] Port should be 8080 (tooling-trusted-releases) via GitHub
  • Re: [I] Port should be 8080 (tooling-trusted-releases) via GitHub
• [INTRO] New contributor – documentation improvements Sanjana
• [I] Improve type validation of GET parameters (tooling-trusted-releases) via GitHub
  • Re: [I] Improve type validation of GET parameters (tooling-trusted-releases) via GitHub
  • Re: [I] Improve type validation of GET parameters (tooling-trusted-releases) via GitHub
• [I] Enforce consistency of enums in Sqlite3 migrations (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce consistency of enums in Sqlite3 migrations (tooling-trusted-releases) via GitHub
  • Re: [I] Enforce consistency of enums in Sqlite3 migrations (tooling-trusted-releases) via GitHub
• [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
  • Re: [PR] fixed issue 477 (tooling-trusted-releases) via GitHub
• [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
  • Re: [I] Implement PyPi Distributions (tooling-trusted-releases) via GitHub
• Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
  • Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
  • Re: [I] Tie ATR server into the rsync path of svn dist artifacts (tooling-trusted-releases) via GitHub
• Re: [I] Provide an api to artifact catalog (tooling-trusted-releases) via GitHub
  • Re: [I] Provide an api to artifact catalog (tooling-trusted-releases) via GitHub
• Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
  • Re: [I] Allow Projects to be defined via .asf.yaml (tooling-trusted-releases) via GitHub
• [I] Watch svn dist releases and catalog changes to projects and releases (tooling-trusted-releases) via GitHub
  • Re: [I] Watch svn dist releases and catalog changes to projects and releases (tooling-trusted-releases) via GitHub
• Meta bug report Jens Geyer
  • Re: Meta bug report Andrew Wetmore
  • Re: Meta bug report Andrew Wetmore
  • Re: Meta bug report Thomas Neidhart
  • Re: Meta bug report Thomas Neidhart
• [I] Catalog projects and releases for each PMC from current data (tooling-trusted-releases) via GitHub
• [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
  • Re: [I] Document identification of generated source files in lightweight and RAT license checks (tooling-trusted-releases) via GitHub
• [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
  • Re: [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
  • Re: [I] Download rsync candidate files by a select tag (tooling-trusted-releases) via GitHub
• [I] Allow files to be tagged in the compose phase according to a mapping (tooling-trusted-releases) via GitHub

• Earlier messages
• Later messages