[
https://issues.apache.org/jira/browse/FLINK-30869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740653#comment-17740653
]
Matthias Pohl commented on FLINK-30869:
---------------------------------------
No worries, happened to me, too. :-) In case, you didn't know, yet: You can use
{{no_push}} in your git configuration for {{master}} if you would like to avoid:
{code}
[remote "origin"]
url = [email protected]:apache/flink.git
fetch = +refs/heads/*:refs/remotes/origin/*
pushurl = no_push
{code}
> Remove remote branches not being used anymore
> ---------------------------------------------
>
> Key: FLINK-30869
> URL: https://issues.apache.org/jira/browse/FLINK-30869
> Project: Flink
> Issue Type: Technical Debt
> Components: Build System
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
>
> {code}
> $ git branch -a | grep 'remotes/origin' | grep -v '/release-'
> remotes/origin/FLINK-30191
> remotes/origin/blink
> remotes/origin/cron-master-dependency_check
> remotes/origin/cron-master-maven_compat
>
> remotes/origin/dependabot/npm_and_yarn/flink-runtime-web/web-dashboard/ua-parser-js-0.7.33
> remotes/origin/exp_github_actions
> remotes/origin/experiment_gha_docs
> remotes/origin/master
> {code}
> There are various remote branches next to {{master}} and the release
> branches. We should either clean those up or document them (maybe in the
> [Release Management
> docs|https://cwiki.apache.org/confluence/display/FLINK/Flink+Release+Management].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
