[
https://issues.apache.org/jira/browse/OAK-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17368900#comment-17368900
]
Konrad Windszus edited comment on OAK-9440 at 6/24/21, 2:54 PM:
----------------------------------------------------------------
You have to use the personal access token when using HTTPS Basic Authentication
(instead of your GitHub password). But instead I would recommend switching to
SSH authentication (for that you have to change the Git remote URL to
{{g...@github.com:apache/jackrabbit-oak.git}} and make sure you upload your
public key to GitHub. Please make sure to thoroughly read
https://docs.github.com/en/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication#using-two-factor-authentication-with-the-command-line
to understand the limitations of 2FA with GitHub.
BTW the same limitations apply to Apache Sling where you committed successfully
already to GitHub...
bq. you volunteered for this undertaking.... and I didn't ask for it
True, but you also didn't oppose. Instead you just didn't vote at all! Also
this is a community and some decision are majority decisions (like this
migration).
was (Author: kwin):
You have to use the personal access token when using HTTPS Basic Authentication
(instead of your GitHub password). But instead I would recommend switching to
SSH authentication (for that you have to change the Git remote URL to
{{g...@github.com:apache/jackrabbit-oak.git}} and make sure you upload your
public key to GitHub. Please make sure to thoroughly read
https://docs.github.com/en/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication#using-two-factor-authentication-with-the-command-line
to understand the limitations of 2FA with GitHub.
bq. you volunteered for this undertaking.... and I didn't ask for it
True, but you also didn't oppose. Instead you just didn't vote at all! Also
this is a community and some decision are majority decisions (like this
migration).
> Migrate Oak from SVN to Git
> ---------------------------
>
> Key: OAK-9440
> URL: https://issues.apache.org/jira/browse/OAK-9440
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Attachments: jackrabbit-check-release-for-gitv1.patch,
> jackrabbit-live-site-migrate-to-gitv1.patch,
> jackrabbit-site-release-for-gitv1.patch
>
>
> # migrate the SVN repository at
> [https://svn.apache.org/repos/asf/jackrabbit/oak/] to a Git repository named
> "jackrabbit-oak" - tracked in INFRA-22016 (/)
> # migrate GitHub SVN mirror at [https://github.com/apache/jackrabbit-oak] to
> mirror the new native Git repo (at Gitbox) - tracked in INFRA-22016 (/)
> # -change the main branch name from "trunk" to "main"-
> # make the SVN repository read only - tracked in INFRA-22016 (/)
> # adjust Jenkins jobs
> ## [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-matrix/]
> (/)
> ## [https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/]
> (/)
> # adjust release check scripts, fixed in r48468 (/)
> ## [https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh]
> attached to [^jackrabbit-check-release-for-gitv1.patch]
> # adjust documentation, this includes
> ## [http://jackrabbit.apache.org/jcr/creating-releases.html] attached to
> [^jackrabbit-site-release-for-gitv1.patch], applied in r1890993 (/)
> ## [https://jackrabbit.apache.org/oak/] (only manually maintained in
> [https://svn.apache.org/repos/asf/jackrabbit/site/live/oak/)|https://svn.apache.org/repos/asf/jackrabbit/site/live/oak/]
> proposed to remove and redirect to /oak/docs instead in
> [^jackrabbit-live-site-migrate-to-gitv1.patch], done in r1890995, (/)
> ## [https://jackrabbit.apache.org/oak/docs/dev_getting_started.html],
> contained in GH PR, (/)
> ## [https://jackrabbit.apache.org/oak/docs/developing-with-git.html],
> contained in GH PR, (/)
> ## ....
> # adjust scm references in pom.xml (/)
> ## primary source should be Gitbox URL (not Github), contained in GH PR
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
