WIP: Explain main-branch dependency selection #19
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/ttyd!19
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/main-dependency-policy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Document main-branch manifest selectors and immutable source selection for builds. Keep repository provenance explicit when coordinating dependencies.
Depends on #18 (
feature/checked-cargo-inputs).FS_METADATA_KNOWN_DEVICE_V1andFS_METADATA_POSIX_REQUIRED_V1, then complete the existing feature acceptance checks.View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.