MAINT: update github workflows files

[Gui-FernandesBR]

Pull request type

Please check the type of change your PR introduces:

• ReadMe, Docs and GitHub maintenance

Pull request checklist

Please check if your PR fulfills the following requirements, depending on the type of PR:

• ReadMe, Docs and GitHub maintenance:

  • Spelling has been verified
  • Code docs are working correctly

What is the current behavior?

The github workflows are not perfect.

What is the new behavior?

They continue not being perfect, but at least now they are updated. Also:

• no longer assigns the issue to its author (only for PRs)
• deleted the useless auto-assign-projects file
• runs the pytest without the [all] option
• assigns @phmbressan as a reviewer in the PRs. I was really missing this.

Does this introduce a breaking change?

• No

Other information

• This PR already works as a test for the current file
• Maybe we could merge master into beta/v1 to catch this little guy: 18ceea1

[phmbressan]

Is this PR really working as intended? You mentioned in the description that it is by itself a test of the new files, but I have not been assigned as a reviewer.

Furthermore, shouldn't the destination branch of this PR be beta/v1.0.0?

[Gui-FernandesBR]

Is this PR really working as intended? You mentioned in the description that it is by itself a test of the new files, but I have not been assigned as a reviewer.

Furthermore, shouldn't the destination branch of this PR be beta/v1.0.0?

You know, since there's no way to test it, sometimes you have to trust that the workflows are gonna work 😅😅😅

• But yes, I can confirm that the same behavior [of you not being assigned as a reviewer yet] happened in the first time we introduced such tests: MAINT: auto assign workflows #214
• Not actually, the maint/update-git-actions was created from the fix/env-analysis-dependency-imports branch, so if I change the direction to beta/v1 it is gonna show way more additions than what is suppose to show. Maybe a good idea is to merge FIX: env analysis dependency imports #403 before this one!

Anyway, many thanks for reviewing it :)
I'm sending a re-review request now

[phmbressan]

I agree with the changes made. Approved.

[Gui-FernandesBR]

Merging it into fix/env-analysis-dependency-imports

[Gui-FernandesBR]

Is this PR really working as intended? You mentioned in the description that it is by itself a test of the new files, but I have not been assigned as a reviewer.
Furthermore, shouldn't the destination branch of this PR be beta/v1.0.0?

You know, since there's no way to test it, sometimes you have to trust that the workflows are gonna work 😅😅😅

• But yes, I can confirm that the same behavior [of you not being assigned as a reviewer yet] happened in the first time we introduced such tests: MAINT: auto assign workflows #214
• Not actually, the maint/update-git-actions was created from the fix/env-analysis-dependency-imports branch, so if I change the direction to beta/v1 it is gonna show way more additions than what is suppose to show. Maybe a good idea is to merge FIX: env analysis dependency imports #403 before this one!

Anyway, many thanks for reviewing it :) I'm sending a re-review request now

Actually, I think the workflow you start working correctly only when it gets to the master branch.
Let's wait a bit more to see.