From 0aebf1cc9fa943304921cd21813533ad1424957a Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Jul 2025 21:07:27 +0000 Subject: [PATCH 1/2] [pre-commit.ci] pre-commit autoupdate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit updates: - [github.com/rbubley/mirrors-prettier: 787fb9f542b140ba0b2aced38e6a3e68021647a3 → 5ba47274f9b181bce26a5150a725577f3c336011](https://github.com/rbubley/mirrors-prettier/compare/787fb9f542b140ba0b2aced38e6a3e68021647a3...5ba47274f9b181bce26a5150a725577f3c336011) --- .pre-commit-config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 5014f9c..eb719e1 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -24,7 +24,7 @@ repos: - id: blacken-docs - repo: https://github.com/rbubley/mirrors-prettier - rev: 787fb9f542b140ba0b2aced38e6a3e68021647a3 # frozen: v3.5.3 + rev: 5ba47274f9b181bce26a5150a725577f3c336011 # frozen: v3.6.2 hooks: - id: prettier files: \.(css|md|yml|yaml) From 253d5369f95bbbcee0774c62aa98e8e921678aef Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Jul 2025 21:12:37 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- .pre-commit-config.yaml | 2 +- content/community/community-outreach.md | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index eb719e1..592f416 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -24,7 +24,7 @@ repos: - id: blacken-docs - repo: https://github.com/rbubley/mirrors-prettier - rev: 5ba47274f9b181bce26a5150a725577f3c336011 # frozen: v3.6.2 + rev: 5ba47274f9b181bce26a5150a725577f3c336011 # frozen: v3.6.2 hooks: - id: prettier files: \.(css|md|yml|yaml) diff --git a/content/community/community-outreach.md b/content/community/community-outreach.md index dce13ac..4062b07 100644 --- a/content/community/community-outreach.md +++ b/content/community/community-outreach.md @@ -7,7 +7,6 @@ title: "Community Outreach" Use various social Media channels for outreach: - Twitter: - - Utilize hashtags relevant to the scientific Python community to increase visibility. - Engage with users by responding to questions, sharing resources, and participating in discussions. - Retweet and mention influential users and organizations to foster connections.