Might also be a good time to think about closing out old PRs (like age > 1.5 years).
On Mon, Jul 6, 2020 at 10:49 PM Otto Fowler <ottobackwa...@gmail.com> wrote: > So, should we rebase our outstanding PR’s? Should all outstanding PR’s > get a note? > > On July 6, 2020 at 17:57:25, Andy LoPresto (alopre...@apache.org) wrote: > > Apache Infra completed the change. Everything looks ok from my end but as I > made the initial change, can someone else verify that their local repo is > good to go? Once that’s done, I’ll update the committer guide and GitHub PR > template with the new language, and check the CI/CD for GitHub Actions too. > Thanks. br/> < > > Andy LoPresto > alopre...@apache.org > alopresto.apa...@gmail.com > He/Him > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > On Jul 6, 2020, at 11:02 AM, Joe Witt <joe.w...@gmail.com> wrote: > > br/>> Looking into this we might be fine. We use thee github 'default > branch' > > which I think you'll get changed by the INFRA ticket. > > br/>> We then might want to look at > https://github.coom/ethomson/retarget_prs > > br/>> Thanks < > > br/>> On Mon, Jul 6, 2020 at 9:21 AM Joe Witt <jooe.w...@gmail.com> > wrote: > > br/>>> Andy < > >> br/>>> I *think* we need to change the githubb actions config a little > bit as > >> well. It defaults to master I believe and we can specify an alternative > >> branch of 'main'. Maybe we just keep an eye on it and see if there is a > >> material difference. One example is the 'build passing' indicator comes > >> from master unless you override it (as I've read previously). > >> br/>>> Thanks < > >> br/>>> On Mon, Jul 6, 2020 at 9:18 AM Andy LooPresto < > alopre...@apache.org> wrote: > >> br/>>>> It appears that we don’t havee the ability to switch the default > branch > >>> ourselves; I’ve filed > https://issues.apache.org/jira/browse/INFRA-20487 > < > >>> https://issues.apache.org/jira/browse/INFRA-20487> requesting Apache > >>> Infra takes care of that. Until that time, committers _should_ merge > the > >>> code to main but I will monitor to ensure we keep the branches in sync. > The > >>> history was moved, the only remaining step is GitHub being aware of the > >>> default branch change. > >>> br/>>>> br/>>>> Andy LoPresto < > >>> alopre...@apache.org > >>> alopresto.apa...@gmail.com > >>> He/Him > >>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > >>> br/>>>>> On Jul 4, 2020, at 11:57 AMM, Joey Frazee > <joey.fra...@icloud.com.INVALID> > >>> wrote: > >>>> br/>>>>> @@alopresto Do you want everyone individually pushing to both > master and > >>> main or are you intending to keep it in sync until it’s made the > default? > >>>> br/>>>>> -joey < > >>>> On Jul 2, 2020, 6:39 PM -0500, alopre...@apache.org, wrote: > >>>>> This is an automated email from the ASF dual-hosted git repository. > >>>>> br/>>>>>> alopresto pusheed a change to branch main > >>>>> in repository https://gitbox.apache.org/repos/asf/nifi.git. > >>>>> br/>>>>>> br/>>>>>> at 239a2e8 NIFFI-7513 Added custom DNS resolution > steps to walkthrough > >>> (#4359) > >>>>> br/>>>>>> No new revisionns were added by this update. > >>>>> br/>>>> br/>>>> br/> < >
