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

Updated workflow #1188

Merged
merged 1 commit into from
Dec 13, 2023
Merged

Conversation

duplixx
Copy link
Member

@duplixx duplixx commented Dec 13, 2023

What kind of change does this PR introduce?

Issue Number:

Fixes #1117

Did you add tests for your changes?

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

Does this PR introduce a breaking change?

Other information

Have you read the contributing guide?

@duplixx duplixx requested a review from palisadoes as a code owner December 13, 2023 05:56
Copy link

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

codecov bot commented Dec 13, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4027f3a) 95.46% compared to head (20727ae) 95.46%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1188   +/-   ##
========================================
  Coverage    95.46%   95.46%           
========================================
  Files          138      138           
  Lines         3328     3328           
  Branches       923      923           
========================================
  Hits          3177     3177           
  Misses         144      144           
  Partials         7        7           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@palisadoes
Copy link
Contributor

  1. Please fill in the PR template properly. We will need to understand why this was done for our records.
  2. Also, please stop opening and then closing PRs. It makes tracking harder for our volunteers with limited time resources. For example I have asked people to take a look at your PRs openly to have them tell me they are closed.

@tasneemkoushar tasneemkoushar merged commit 15fff09 into PalisadoesFoundation:develop Dec 13, 2023
@palisadoes
Copy link
Contributor

We have to revert this. It is not being applied to the deltas

palisadoes added a commit that referenced this pull request Dec 13, 2023
palisadoes added a commit that referenced this pull request Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants