Add contribution demo file for GitHub workflow demonstration#11574
Open
wearedood wants to merge 2 commits intocelo-org:masterfrom
Open
Add contribution demo file for GitHub workflow demonstration#11574wearedood wants to merge 2 commits intocelo-org:masterfrom
wearedood wants to merge 2 commits intocelo-org:masterfrom
Conversation
This demonstrates the GitHub fork and pull request workflow for contributing to the Celo monorepo project.
Contributor
|
This PR is stale and will be closed in 30 days without activity |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Description
This pull request demonstrates the GitHub contribution workflow by adding a simple demo file. This is part of learning the standard fork-and-pull-request process for contributing to open source projects.
Changes Made
Testing
This is a documentation/demo file addition that doesn't require functional testing. The file has been reviewed for proper markdown formatting and content accuracy.
Related Issues
This is a learning exercise for GitHub contribution workflow - no specific issues addressed.What is the current behavior, and what is the updated/expected behavior with this PR?_
Other changes
Describe any minor or "drive-by" changes here.
Tested
An explanation of how the changes were tested or an explanation as to why they don't need to be.
Related issues
Backwards compatibility
Brief explanation of why these changes are/are not backwards compatible.
Documentation
The set of community facing docs that have been added/modified because of this change