This is a commit that actually should not be merged.
#2
Closed
juga
wants to merge 1 commits from juga/pEpPythonAdapter_test:issue1_gitea_test into master
Loading…
Reference in New Issue
There is no content yet.
Delete Branch 'juga/pEpPythonAdapter_test:issue1_gitea_test'
Deleting a branch is permanent. It CANNOT be undone. Continue?
Just to show how cloning a repo in gitea, creating a new branch and
asking to merge via a Pull Request would work.
I can also say:
Closes #1
and the issue with that number would be automatically closed when this
branch is merged.
@heck, @nkls, ^This text has been automatically created by gitea from the one commit in my branch https://gitea.pep.foundation/juga/pEpPythonAdapter_test/src/branch/issue1_gitea_test, after cloning this repo, new branch, commit, and create a new Pull Request going to Pull Requests tab and comparing the branch i want to merge from my clone to the "destination" ("canonical") repo branch: https://gitea.pep.foundation/dvn/pEpPythonAdapter/compare/master...juga:issue1_gitea_test
When there're several commits the branch to merge that differ from the destination, this text would be empty, and i can write a summary of the commits.
@ -16,2 +16,4 @@GPLv3## A sectionAnd now i can "start a review" and comment directly the code.
I can also make other general comment on the PR. codeberg.org, Gitlab, github.com, they all work in this similar way.
Closing cause repo has been migrated here.