-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #17 from Mastercard/mbepUploads
Mbep uploads
- Loading branch information
Showing
27 changed files
with
4,118 additions
and
3,471 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
# Change Log | ||
|
||
## Version 1.0.0 | ||
|
||
June 22, 2021 | ||
|
||
Changes: | ||
|
||
# Change Log | ||
|
||
## Version 1.0.0 | ||
|
||
June 22, 2021 | ||
|
||
Changes: | ||
|
||
* Initial release |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,25 @@ | ||
# Contributing | ||
|
||
### Submitting Changes | ||
|
||
1. Fork the repository | ||
2. Create your feature branch (git checkout -b my-new-feature) | ||
3. Commit your changes (git commit -am 'Add some feature') | ||
4. Execute the unit tests to ensure all pass | ||
5. Squash your commits (git rebase --interactive --autosquash) | ||
6. Push the branch (git push origin my-new-feature) | ||
7. Create a new Pull Request | ||
|
||
### Pull request Approval | ||
|
||
Internal developers will verify the changes and approve the request or leave comments for improvements. | ||
|
||
### Quality Expectations | ||
Please ensure any contributions include unit tests. The project maintains a high level of test coverage for its functionality. | ||
Submissions are expected to maintain a similar level of coverage. | ||
|
||
## How to engage Maintainers | ||
Leaving Issues using the issue tracker in GitHub. | ||
Maintainers will look for issues posted to the repository and will resolve the issue as soon as possible. | ||
|
||
# Contributing | ||
|
||
### Submitting Changes | ||
|
||
1. Fork the repository | ||
2. Create your feature branch (git checkout -b my-new-feature) | ||
3. Commit your changes (git commit -am 'Add some feature') | ||
4. Execute the unit tests to ensure all pass | ||
5. Squash your commits (git rebase --interactive --autosquash) | ||
6. Push the branch (git push origin my-new-feature) | ||
7. Create a new Pull Request | ||
|
||
### Pull request Approval | ||
|
||
Internal developers will verify the changes and approve the request or leave comments for improvements. | ||
|
||
### Quality Expectations | ||
Please ensure any contributions include unit tests. The project maintains a high level of test coverage for its functionality. | ||
Submissions are expected to maintain a similar level of coverage. | ||
|
||
## How to engage Maintainers | ||
Leaving Issues using the issue tracker in GitHub. | ||
Maintainers will look for issues posted to the repository and will resolve the issue as soon as possible. | ||
|
||
**Copyright © 1994-2021, All Rights Reserved by Mastercard.** |
Oops, something went wrong.