Skip to content

Conversation

ivergara
Copy link
Collaborator

Allowing fork-pull workflow

Allowing fork-pull workflow
@codecov
Copy link

codecov bot commented Jun 16, 2023

Codecov Report

Merging #163 (af6bc65) into main (4aa3706) will decrease coverage by 57.23%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #163       +/-   ##
===========================================
- Coverage   93.73%   36.51%   -57.23%     
===========================================
  Files          16       16               
  Lines        1835     1835               
===========================================
- Hits         1720      670     -1050     
- Misses        115     1165     +1050     

see 14 files with indirect coverage changes

steps:
- name: Checkout branch
uses: actions/checkout@v3
with:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would we also need to remove this for all of the respective integration tests?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say so

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

More removals
uses: actions/checkout@v3
with:
ref: ${{ github.head_ref }}
fetch-depth: 0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: This fetches the entire history. Is this to run some backwards compatibility test?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean it should be fetch-depth: 1? Which most likely is the default I guess.

I don't think there is any good reason why we do this.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah might be better to just remove the entire with block for simplicity.

Copy link
Member

@pavelzw pavelzw Jun 16, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think fetch-depth is used in our repositories because setuptools-scm uses Git tags to determine the version when building and most our projects use it for packaging.

Default depth
Copy link
Collaborator

@kklein kklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for looking into this!

@ivergara ivergara merged commit 31d8574 into main Jun 16, 2023
@ivergara ivergara deleted the ivergara-patch-1 branch June 16, 2023 15:08
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.

4 participants