-
Notifications
You must be signed in to change notification settings - Fork 26
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 #35 from frankodoom/development
Development
- Loading branch information
Showing
29 changed files
with
20,504 additions
and
19,183 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 |
---|---|---|
@@ -0,0 +1,35 @@ | ||
name: DEV-WORKFLOW-ACTION | ||
|
||
on: | ||
push: | ||
branches: [ development ] | ||
pull_request: | ||
branches: [ development ] | ||
|
||
jobs: | ||
build: | ||
runs-on: windows-latest | ||
steps: | ||
- uses: actions/checkout@v2 | ||
- name: Setup .NET | ||
uses: actions/setup-dotnet@v1 | ||
with: | ||
dotnet-version: 8.x.x | ||
- name: Restore Workload dependencies | ||
run: dotnet workload restore | ||
# - name: Install .NET Maui workload packs | ||
# run: dotnet workload install maui android | ||
- name: Restore NuGet packages | ||
run: dotnet restore | ||
- name: Build | ||
run: dotnet build | ||
- name: Test | ||
run: dotnet test --no-build --verbosity normal /p:CollectCoverage=true /p:CoverletOutputFormat=cobertura /p:CoverletOutput=TestResults/ --collect:"XPlat Code Coverage" | ||
- name: Upload coverage reports to Codecov | ||
uses: codecov/[email protected] | ||
with: | ||
token: ${{ secrets.CODECOV_TOKEN }} | ||
file: ./TestResults/coverage.cobertura.xml | ||
flags: unittests | ||
name: codecov-umbrella | ||
#fail_ci_if_error: true |
This file was deleted.
Oops, something went wrong.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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 |
---|---|---|
@@ -0,0 +1,36 @@ | ||
|
||
# Code of Conduct | ||
|
||
## Our Pledge | ||
|
||
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a positive experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. | ||
|
||
## Our Standards | ||
|
||
Examples of behavior that contribute to creating a positive environment include: | ||
|
||
- Using welcoming and inclusive language | ||
- Being respectful of differing viewpoints and experiences | ||
- Gracefully accepting constructive criticism | ||
- Focusing on what is best for the community | ||
- Showing empathy towards other community members | ||
|
||
Examples of unacceptable behavior by participants include: | ||
|
||
- The use of sexualized language or imagery and unwelcome sexual attention or advances | ||
- Trolling, insulting/derogatory comments, and personal or political attacks | ||
- Public harassment | ||
- Publishing others' private information, such as a physical or electronic address, without explicit permission | ||
- Other conduct which could reasonably be considered inappropriate in a professional setting | ||
|
||
## Our Responsibilities | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. | ||
|
||
## Enforcement | ||
|
||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at [INSERT CONTACT METHOD HERE]. All complaints will be reviewed and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. | ||
|
||
## Attribution | ||
|
||
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/ |
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 |
---|---|---|
@@ -0,0 +1,48 @@ | ||
|
||
|
||
# Contributing to CountryData.Net | ||
|
||
Thank you for considering contributing to CountryData.Net We appreciate all forms of contributions, whether it's fixing bugs, adding new features, updating documentation, or even just discussing ideas. Your input is invaluable to us. | ||
|
||
## Getting Started | ||
|
||
Before you start contributing, please go through our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a positive experience for everyone involved. | ||
|
||
### How Can I Contribute? | ||
|
||
There are many ways you can contribute to CountryData.Net: | ||
|
||
#### Reporting Bugs | ||
|
||
If you find a bug, please create an issue on GitHub. Make sure to describe the problem in detail, including steps to reproduce the issue, what you expect to happen, and what actually happens. | ||
|
||
#### Suggesting Enhancements | ||
|
||
For feature requests and enhancements, open an issue first to discuss the change you wish to make. This allows us to better coordinate efforts, prevent duplicate work, and help define the scope of the proposal. | ||
|
||
#### Creating Pull Requests | ||
|
||
Pull requests are the best way to propose changes to the project. They allow us to review your modifications before merging them into the main branch. Please follow these steps to create a pull request: | ||
|
||
1. Fork the Project Repository, *Note* Fork from `development` branch. | ||
2. Create a new branch for your changes. | ||
3. Commit your changes to the new branch. | ||
4. Push your branch to GitHub. | ||
5. Open a Pull Request against the original repository. | ||
|
||
Please ensure your pull request adheres to the following rules: | ||
|
||
- Each pull request should implement one feature or fix a bug. | ||
- Avoid mixing unrelated changes. | ||
- Update the README.md with details of changes to the interface. | ||
- Increase coverage by writing unit tests. | ||
- Check existing open issues/pull requests first to avoid duplicating effort. | ||
|
||
### Style Guide | ||
|
||
- Follow the existing style guide. Consistency is key! | ||
- Keep commits small and focused. Large commits are hard to review and often lead to merge conflicts. | ||
- Write meaningful commit messages. Good practice is to write clear, concise messages that explain what was changed and why. | ||
|
||
|
||
Remember, every contribution counts, no matter how big or small. Thank you for taking the time to improve CountryData.Net! |
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
Oops, something went wrong.