dev  

Messages by Thread

• • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
  • Re: [I] Preserve the history of configuration options that affect attestations (tooling-trusted-releases) via GitHub
• Re: [I] Track creator and editor asf user ids in the database (tooling-trusted-releases) via GitHub
  • Re: [I] Track creator and editor asf user ids in the database (tooling-trusted-releases) via GitHub
• [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
  • Re: [I] Record when committees are automatically updated (tooling-trusted-releases) via GitHub
• Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
  • Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
  • Re: [I] Add REVISION as a usable variable in emails (tooling-trusted-releases) via GitHub
• [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
  • Re: [I] Allow substitution variables to be used in email subjects (tooling-trusted-releases) via GitHub
• Re: [I] Allow revisions to be tagged (tooling-trusted-releases) via GitHub
  • Re: [I] Allow revisions to be tagged (tooling-trusted-releases) via GitHub
  • Re: [I] Allow revisions to be tagged (tooling-trusted-releases) via GitHub
• [I] Add active polling of check completion status in the compose phase (tooling-trusted-releases) via GitHub
  • Re: [I] Add active polling of check completion status in the compose phase (tooling-trusted-releases) via GitHub
  • Re: [I] Add active polling of check completion status in the compose phase (tooling-trusted-releases) via GitHub
• [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
  • Re: [I] Ordering of private vs public functions (tooling-trusted-releases) via GitHub
• [PR] pre-commit light use global `node_modules` exclude (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit light use global `node_modules` exclude (tooling-trusted-releases) via GitHub
  • Re: [PR] pre-commit light use global `node_modules` exclude (tooling-trusted-releases) via GitHub
• [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
  • Re: [I] Ensure that JS packages are installed using recommended security practices (tooling-trusted-releases) via GitHub
• [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
  • Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
  • Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
  • Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
  • Re: [I] We could use `prettier` with `pre-commit` to auto format some file types to stop all the on-going debates over styles (tooling-trusted-releases) via GitHub
• [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
  • Re: [PR] Add markdownlint with pre-commit (tooling-trusted-releases) via GitHub
• [PR] pre-commit autoupdate; standardize and add docs (tooling-docs) via GitHub
  • Re: [PR] pre-commit autoupdate; standardize and add docs (tooling-docs) via GitHub
  • Re: [PR] pre-commit autoupdate; standardize and add docs (tooling-docs) via GitHub
• [PR] Added macOS instructions (tooling-trusted-releases) via GitHub
  • Re: [PR] Added macOS instructions (tooling-trusted-releases) via GitHub
• [I] Add foundation logo to the website (tooling-trusted-releases) via GitHub
  • Re: [I] Add foundation logo to the website (tooling-trusted-releases) via GitHub
  • Re: [I] Add foundation logo to the website (tooling-trusted-releases) via GitHub
  • Re: [I] Add foundation logo to the website (tooling-trusted-releases) via GitHub
  • Re: [I] Add foundation logo to the website (tooling-trusted-releases) via GitHub
• [I] Potential improvements saved for discussion (tooling-trusted-releases) via GitHub
  • Re: [I] Resolve the design of emptiness and nullability for form types (tooling-trusted-releases) via GitHub
  • Re: [I] Resolve the design of emptiness and nullability for form types (tooling-trusted-releases) via GitHub
• [I] Replace public release and committee pages with a catalog page (tooling-trusted-releases) via GitHub
  • Re: [I] Replace public release and committee pages with a catalog page (tooling-trusted-releases) via GitHub
  • Re: [I] Replace public release and committee pages with a catalog page (tooling-trusted-releases) via GitHub
• [I] Download artifacts should be on the public left nav (tooling-trusted-releases) via GitHub
  • Re: [I] Download artifacts should be on the public left nav (tooling-trusted-releases) via GitHub
  • Re: [I] Download artifacts should be on the public left nav (tooling-trusted-releases) via GitHub
• [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
  • Re: [I] Provide access to documentation without needing to login (tooling-trusted-releases) via GitHub
• [I] Improve the UX for voting (tooling-trusted-releases) via GitHub
  • Re: [I] Improve the UX for voting (tooling-trusted-releases) via GitHub
  • Re: [I] Improve the UX for voting (tooling-trusted-releases) via GitHub
  • Re: [I] Improve the UX for voting (tooling-trusted-releases) via GitHub
• [I] Work on the following issues in order (tooling-trusted-releases) via GitHub
  • Re: [I] Work on the following issues in order (tooling-trusted-releases) via GitHub
  • Re: [I] Work on the following issues in order (tooling-trusted-releases) via GitHub
• Re: [I] aiohttp.client_exceptions.InvalidUrlClientError: commit/svn (tooling-trusted-releases) via GitHub
  • Re: [I] aiohttp.client_exceptions.InvalidUrlClientError: commit/svn (tooling-trusted-releases) via GitHub
• [PR] Add note about f-string code convention (tooling-trusted-releases) via GitHub
  • Re: [PR] Add note about f-string code convention (tooling-trusted-releases) via GitHub
• [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
  • Re: [I] Add Markdown linting (tooling-trusted-releases) via GitHub
• [I] Migrate to Python 3.14 (tooling-trusted-releases) via GitHub
  • Re: [I] Migrate to Python 3.14 (tooling-trusted-releases) via GitHub
• [PR] Use multiple lines for paragraphs (tooling-trusted-releases) via GitHub
  • Re: [PR] Use multiple lines for paragraphs (tooling-trusted-releases) via GitHub
  • Re: [PR] Use multiple lines for paragraphs (tooling-trusted-releases) via GitHub
  • Re: [PR] Use multiple lines for paragraphs (tooling-trusted-releases) via GitHub
  • Re: [PR] Use multiple lines for paragraphs (tooling-trusted-releases) via GitHub
• [I] promote uploading via GHA (tooling-trusted-releases) via GitHub
  • Re: [I] promote uploading via GHA (tooling-trusted-releases) via GitHub
  • Re: [I] promote uploading via GHA (tooling-trusted-releases) via GitHub
  • Re: [I] promote uploading via GHA (tooling-trusted-releases) via GitHub
  • Re: [I] promote uploading via GHA (tooling-trusted-releases) via GitHub
• [PR] Update docs for WTForms -> Pydantic; fixes #338 (tooling-trusted-releases) via GitHub
  • [GH] Update docs for WTForms -> Pydantic; fixes #338 (tooling-trusted-releases) via GitHub
  • Re: [PR] Update docs for WTForms -> Pydantic; fixes #338 (tooling-trusted-releases) via GitHub
  • Re: [PR] Update docs for WTForms -> Pydantic; fixes #338 (tooling-trusted-releases) via GitHub
• [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
  • Re: [I] Document the checks made by ATR (tooling-trusted-releases) via GitHub
• [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] check for zip bombs in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] Check for bombs and other archival problems in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] Check for bombs and other archival problems in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] Check for bombs and other archival problems in uploads (tooling-trusted-releases) via GitHub
  • Re: [I] Check for bombs and other archival problems in uploads (tooling-trusted-releases) via GitHub
• [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
  • Re: [I] allow Incubator PMC members to use the tool for all podlings (tooling-trusted-releases) via GitHub
• [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
  • Re: [I] Document why f-strings are used for logging calls (tooling-trusted-releases) via GitHub
• Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
  • Re: [I] Fix the APPLICATION DATA AFTER CLOSE NOTIFY error in Hypercorn (tooling-trusted-releases) via GitHub
• [I] Update docs for WTForms -> Pydantic move (tooling-trusted-releases) via GitHub
  • Re: [I] Update docs for WTForms -> Pydantic move (tooling-trusted-releases) via GitHub
  • Re: [I] Update docs for WTForms -> Pydantic move (tooling-trusted-releases) via GitHub
• [PR] Hypercorn crashes and does not reload when saving files #320 (tooling-trusted-releases) via GitHub
  • [GH] Hypercorn crashes and does not reload when saving files #320 (tooling-trusted-releases) via GitHub
  • [GH] Hypercorn crashes and does not reload when saving files #320 (tooling-trusted-releases) via GitHub
  • Re: [PR] Hypercorn crashes and does not reload when saving files #320 (tooling-trusted-releases) via GitHub
• [PR] Make the draft forms more type safe (tooling-trusted-releases) via GitHub
  • [GH] Make the draft forms more type safe (tooling-trusted-releases) via GitHub

• Earlier messages
• Later messages