lulianqi opened a new pull request, #1:
URL: https://github.com/apache/dubbo-net/pull/1

   ## Summary
   
   This PR proposes the initial import of DubboNet from 
[lulianqi/DubboNet](https://github.com/lulianqi/DubboNet) into 
`apache/dubbo-net`, preserving the existing Git history.
   
   - Source: `lulianqi/DubboNet:master` at 
`0a451f94fb45fb1acbd3b9b576f37c7c01e5edf1` (pre-ASF version 3.6.2).
   - Preserves all **131 commits reachable from the source master**, with their 
existing SHAs and authorship.
   - Joins the source history with Apache's initialization commit 
`7e3cfea14b5a54d6d8259a6c161ddf054e608f80` using a merge commit; no history 
rewrite or force push.
   - Preserves the Apache-provided `.asf.yaml` unchanged and resolves the 
README add/add conflict by retaining the existing usage documentation.
   - Runtime source code, examples, tests, protocol documentation, and the 
original license/attributions are unchanged.
   - Updates the package's project/repository URLs to 
`https://github.com/apache/dubbo-net`.
   - Restricts the inherited personal publishing job to `github.repository == 
'lulianqi/DubboNet'`, so it cannot run in Apache or fork repositories with the 
previous personal publishing identity. No credentials have been copied and no 
package has been published.
   
   The two new commits are:
   1. `e0ccc3b3c31f409011292948d5267da7750ff7b0` — join the two histories.
   2. `124e3db54d4ef4bb47db1d477b8d042cdd2a559c` — repository URLs and the 
legacy publishing guard.
   
   ## Important: merge strategy
   
   **Please use “Create a merge commit”, not “Squash and merge” or “Rebase and 
merge”.** Keeping the original commit identities and history is a primary 
purpose of this import.
   
   ## Validation
   
   - `dotnet build DubboNet.sln --configuration Release 
-p:GeneratePackageOnBuild=false --nologo` — passed (0 errors; existing .NET 6 
EOL / compiler / analyzer warnings remain).
   - `dotnet test Tests/UnitTestForDubboNet/UnitTestForDubboNet.csproj 
--configuration Release --no-build --no-restore 
-p:GeneratePackageOnBuild=false` — **236 passed, 0 failed, 0 skipped**.
   - Verified that the original master is an ancestor of the import branch and 
no original master commits are missing.
   - Verified that the Apache initialization commit is an ancestor and 
`.asf.yaml` is unchanged.
   - `git fsck --connectivity-only --no-dangling HEAD` and `git diff --check` — 
passed.
   - Parsed the workflow YAML and verified the repository guard.
   - No live external Provider integration tests were run for this import; 
examples and the integration-test project were built, not executed.
   
   ## Maintainer review / follow-up
   
   - [ ] Confirm the applicable code-acceptance / IP-clearance and 
contributor-agreement requirements before merging. This PR does not assert that 
those administrative steps are already complete.
   - [ ] Review the licensing transition, NOTICE, source headers, and 
third-party notices. The existing MIT license and attributions are 
intentionally preserved here rather than unilaterally rewritten.
   - [ ] Establish ASF-compliant CI and release publishing, including 
review/pinning of external Actions and the NuGet publishing 
identity/permissions.
   - [ ] Decide whether to import the old release branches and tags separately. 
A PR carries reachable commits, not the other branch/tag references; those have 
**not** been pushed to the Apache repository.
   - [ ] Keep pre-ASF tags/packages distinct from future approved Apache 
releases.
   
   The original personal repository, its branches/tags, GitHub Issues/Releases, 
and NuGet ownership are not modified by this PR.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to