Contributions possible due gitea configuration #368

Open
stappers wants to merge 1 commits from stappers/meli:idp into master

What I today learnt on IRC

12:39 < stappers> How to "merge request"?  ( or how to get beyond the 404 from
    https://codeberg.org/meli/meli/compare/master...stappers/meli:debchangelog
    ? )
13:53 < manospitsid> stappers: I think merge requests in codeberg
    are turned off since it is only a mirror, you'd have to do it on
    the main repository (you can login with your codeberg account,
    no sign-up necessary)
14:00 < stappers> ( The owner has already reached the limit of 0 repositories.
    ( I will try harder. ) )
14:01 < manospitsid> oh
14:01 < manospitsid> did you try creating a new repo? try creating a fork of
    meli
14:01 < manospitsid> instead
14:03 < stappers> a fork of meli:  https://codeberg.org/stappers/meli/
14:04 < manospitsid> I mean creating a new fork on git.meli-email.org
14:05 < manospitsid> then you can add it as a remote in your local repository
    for example
14:05 < manospitsid> git remote add origin2 git://...
14:05 < stappers> There is now https://git.meli-email.org/stappers/meli
14:05  * stappers continues with the merge request

Signed-off-by: Geert Stappers stappers@stappers.it

What I today learnt on IRC ```text 12:39 < stappers> How to "merge request"? ( or how to get beyond the 404 from https://codeberg.org/meli/meli/compare/master...stappers/meli:debchangelog ? ) 13:53 < manospitsid> stappers: I think merge requests in codeberg are turned off since it is only a mirror, you'd have to do it on the main repository (you can login with your codeberg account, no sign-up necessary) 14:00 < stappers> ( The owner has already reached the limit of 0 repositories. ( I will try harder. ) ) 14:01 < manospitsid> oh 14:01 < manospitsid> did you try creating a new repo? try creating a fork of meli 14:01 < manospitsid> instead 14:03 < stappers> a fork of meli: https://codeberg.org/stappers/meli/ 14:04 < manospitsid> I mean creating a new fork on git.meli-email.org 14:05 < manospitsid> then you can add it as a remote in your local repository for example 14:05 < manospitsid> git remote add origin2 git://... 14:05 < stappers> There is now https://git.meli-email.org/stappers/meli 14:05 * stappers continues with the merge request ``` Signed-off-by: Geert Stappers <stappers@stappers.it>
stappers added 1 commit 2024-03-10 19:42:28 +02:00
763015f965 Contributions possible due gitea configuration
What I today learnt on IRC
12:39 < stappers> How to "merge request"?  ( or how to get beyond the 404 from
    https://codeberg.org/meli/meli/compare/master...stappers/meli:debchangelog
    ? )
13:53 < manospitsid> stappers: I think merge requests in codeberg
    are turned off since it is only a mirror, you'd have to do it on
    the main repository (you can login with your codeberg account,
    no sign-up necessary)
14:00 < stappers> ( The owner has already reached the limit of 0 repositories.
    ( I will try harder. ) )
14:01 < manospitsid> oh
14:01 < manospitsid> did you try creating a new repo? try creating a fork of
    meli
14:01 < manospitsid> instead
14:03 < stappers> a fork of meli:  https://codeberg.org/stappers/meli/
14:04 < manospitsid> I mean creating a new fork on git.meli-email.org
14:05 < manospitsid> then you can add it as a remote in your local repository
    for example
14:05 < manospitsid> git remote add origin2 git://...
14:05 < stappers> There is now https://git.meli-email.org/stappers/meli
14:05  * stappers continues with the merge request

Signed-off-by: Geert Stappers <stappers@stappers.it>
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b stappers-idp master
git pull idp

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff stappers-idp
git push origin master
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: meli/meli#368
There is no content yet.