yea I think we should, but no need to worry too much about it because
gitbox still works in the release scripts.
On Tue, Aug 27, 2019 at 3:23 AM Shane Knapp wrote:
> revisiting this old thread...
>
> i noticed from the committers' page on the spark site that the 'apache'
> remote should be 'gith
revisiting this old thread...
i noticed from the committers' page on the spark site that the 'apache'
remote should be 'github.com', and not 'gitbox' as instructed here.
so, i did a quick check of the spark repo and found we're still referencing
gitbox in a few places:
➜ spark git:(fix-run-tests
Yes, we all need to be using one remote, and that should be github.
The website is authoritative. this became clear after the initial
email. I apologize as I don't think this was made extra clear to all
committers, and it is important. I see that there are some checks in
the sync to even deal with
The above instruction is different from what the website document:
https://github.com/apache/spark-website/commit/92606b2e7849b9d743ef2a8176438142420a83e5#diff-17faa4bab13b7530a3e1b627bb798ad0
Some committers are using gitbox, but the others are following the website
instruction and using github.
Similar issues are going on in spark-website as well. I also filed a ticket
at https://issues.apache.org/jira/browse/INFRA-17469.
2018년 12월 12일 (수) 오전 9:02, Reynold Xin 님이 작성:
> I filed a ticket: https://issues.apache.org/jira/browse/INFRA-17403
>
> Please add your support there.
>
>
> On Tue, De
I filed a ticket: https://issues.apache.org/jira/browse/INFRA-17403
Please add your support there.
On Tue, Dec 11, 2018 at 4:58 PM, Sean Owen < sro...@apache.org > wrote:
>
> I asked on the original ticket at https:/ / issues. apache. org/ jira/ browse/
> INFRA-17385 ( https://issues.apache.org
I asked on the original ticket at
https://issues.apache.org/jira/browse/INFRA-17385 but no follow-up. Go
ahead and open a new INFRA ticket.
On Tue, Dec 11, 2018 at 6:20 PM Reynold Xin wrote:
> Thanks, Sean. Which INFRA ticket is it? It's creating a lot of noise so I
> want to put some pressure m
Me too. I want to put some input as well if that can be helpful.
On Wed, 12 Dec 2018, 8:20 am Reynold Xin Thanks, Sean. Which INFRA ticket is it? It's creating a lot of noise so I
> want to put some pressure myself there too.
>
>
> On Mon, Dec 10, 2018 at 9:51 AM, Sean Owen wrote:
>
>> Agree, I'
Thanks, Sean. Which INFRA ticket is it? It's creating a lot of noise so I want
to put some pressure myself there too.
On Mon, Dec 10, 2018 at 9:51 AM, Sean Owen < sro...@apache.org > wrote:
>
>
>
> Agree, I'll ask on the INFRA ticket and follow up. That's a lot of extra
> noise.
>
>
>
> On
Ah, sorry. I missed it. It works correctly. Thanks.
2018년 12월 11일 (화) 오전 10:47, Sean Owen 님이 작성:
> Did you do the step where you sync your GitHub and ASF account? After an
> hour you should get an email and then you can.
>
> On Mon, Dec 10, 2018, 8:01 PM Hyukjin Kwon
>> BTW, should I be able to
Did you do the step where you sync your GitHub and ASF account? After an
hour you should get an email and then you can.
On Mon, Dec 10, 2018, 8:01 PM Hyukjin Kwon BTW, should I be able to close PRs via GitHub UI right now or is there
> another way to do it? Looks I'm not seeing the close button.
BTW, should I be able to close PRs via GitHub UI right now or is there
another way to do it? Looks I'm not seeing the close button.
2018년 12월 11일 (화) 오전 1:51, Sean Owen 님이 작성:
> Agree, I'll ask on the INFRA ticket and follow up. That's a lot of extra
> noise.
>
> On Mon, Dec 10, 2018 at 11:37 AM
Agree, I'll ask on the INFRA ticket and follow up. That's a lot of extra noise.
On Mon, Dec 10, 2018 at 11:37 AM Marcelo Vanzin wrote:
>
> Hmm, it also seems that github comments are being sync'ed to jira.
> That's gonna get old very quickly, we should probably ask infra to
> disable that (if we
Hmm, it also seems that github comments are being sync'ed to jira.
That's gonna get old very quickly, we should probably ask infra to
disable that (if we can't do it ourselves).
On Mon, Dec 10, 2018 at 9:13 AM Sean Owen wrote:
>
> Update for committers: now that my user ID is synced, I can
> succe
Update for committers: now that my user ID is synced, I can
successfully push to remote https://github.com/apache/spark directly.
Use that as the 'apache' remote (if you like; gitbox also works). I
confirmed the sync works both ways.
As a bonus you can directly close pull requests when needed inst
15 matches
Mail list logo
