Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mbep uploads #17

Merged
merged 5 commits into from
May 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions CHANGELOG.md
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
48 changes: 24 additions & 24 deletions CONTRIBUTING.md
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.**
400 changes: 200 additions & 200 deletions LICENSE

Large diffs are not rendered by default.

324 changes: 169 additions & 155 deletions README.md

Large diffs are not rendered by default.

Loading
Loading