Skip to content

Conversation

@shahar1
Copy link
Contributor

@shahar1 shahar1 commented Jan 10, 2026

Following a past unfortunate experience - I think that it's important to notify PR authors regarding:

  • Public visibility of their name and email addresses once PRs are merged.
  • The fact that once merged - removal or changing is irreversible.
  • GitHub's method to anonymize commit's email addresses.

Was generative AI tooling used to co-author this PR?

  • Yes (please specify the tool below)
    ChatGPT for proofreading

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Jan 10, 2026
@shahar1 shahar1 force-pushed the add-privacy-caution-to-pr-guideliens branch from de0dcec to 5ab21ea Compare January 10, 2026 09:23
@shahar1 shahar1 marked this pull request as draft January 10, 2026 09:24
@shahar1 shahar1 force-pushed the add-privacy-caution-to-pr-guideliens branch 5 times, most recently from f818ee7 to a3fd9a0 Compare January 10, 2026 09:50
@shahar1 shahar1 marked this pull request as ready for review January 10, 2026 09:51
@shahar1 shahar1 changed the title Add privacy caution to PR guidelines and template Add a privacy section to PR guidelines and template Jan 10, 2026
@shahar1 shahar1 requested review from jscheffl and potiuk January 10, 2026 09:52
@shahar1 shahar1 force-pushed the add-privacy-caution-to-pr-guideliens branch 7 times, most recently from 994dc81 to 596ad4a Compare January 10, 2026 14:13
@shahar1 shahar1 marked this pull request as draft January 10, 2026 14:14
@shahar1 shahar1 force-pushed the add-privacy-caution-to-pr-guideliens branch from 596ad4a to 7483bd9 Compare January 10, 2026 14:16
@shahar1 shahar1 marked this pull request as ready for review January 10, 2026 14:25
Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
@shahar1 shahar1 force-pushed the add-privacy-caution-to-pr-guideliens branch from 7483bd9 to 90c9c5c Compare January 10, 2026 15:34
@shahar1 shahar1 merged commit 7f855d7 into apache:main Jan 10, 2026
61 checks passed
@shahar1 shahar1 deleted the add-privacy-caution-to-pr-guideliens branch January 10, 2026 15:46
github-actions bot pushed a commit that referenced this pull request Jan 10, 2026
(cherry picked from commit 7f855d7)

Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
@github-actions
Copy link

Backport successfully created: v3-1-test

Status Branch Result
v3-1-test PR Link

github-actions bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Jan 10, 2026
…#60367)

(cherry picked from commit 7f855d7)

Co-authored-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
shahar1 pushed a commit that referenced this pull request Jan 10, 2026
#60371)

(cherry picked from commit 7f855d7)

Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
ephraimbuddy pushed a commit that referenced this pull request Jan 13, 2026
#60371)

(cherry picked from commit 7f855d7)

Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
ephraimbuddy pushed a commit that referenced this pull request Jan 14, 2026
#60371)

(cherry picked from commit 7f855d7)

Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
ephraimbuddy pushed a commit that referenced this pull request Jan 16, 2026
#60371)

(cherry picked from commit 7f855d7)

Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
jason810496 pushed a commit to jason810496/airflow that referenced this pull request Jan 22, 2026
Signed-off-by: Shahar Epstein <60007259+shahar1@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants