We should try to follow the same workflow of all the other projects: <ul dir="auto

Rather than starting from scratch, <a href="https://github.com/jandelgado/golang-ci-te

<a class="user-mention notranslate" data-hovercard-type="user" data-hover

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

CI requirements about go-intelowl HOT 4 CLOSED

mlodic commented on August 17, 2024 1

CI requirements

from go-intelowl.

Comments (4)

spiderxm commented on August 17, 2024 3

Assign me this issue

from go-intelowl.

CITIZENDOT commented on August 17, 2024 2

Rather than starting from scratch, This could be a reference for contributors.
It includes (with minor changes)

using master branch only for pushing new releases from the develop branch
using develop branch as base repository and create new branches for new features from this branch
adding linters for go code
Running tests

And also Code Coverage

from go-intelowl.

eshaan7 commented on August 17, 2024 1

@mlodic, @eshaan7. Please create a develop branch. Then in future will raise pr only in develop branch.

I think we can create a develop branch once we have atleast a working prototype and the first alpha release of this.
No point in managing 2 branches for now.

from go-intelowl.

spiderxm commented on August 17, 2024

@mlodic, @eshaan7. Please create a develop branch. Then in future will raise pr only in develop branch.

from go-intelowl.

Recommend Projects