Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@nvuillam
Copy link
Contributor

All is in the title :)

Checklist

Not all of these might apply to your change but the more you are able to check
the easier it will be to get your contribution merged.

  • CI passes
  • Description of proposed change
  • Documentation (README, docs/, man pages) is updated
  • Existing issue is referenced if there is one
  • Unit tests for the proposed change

@abitrolly
Copy link

I guess you might interested to support this project more than others. If that's correct, then I bet you want to be aware of #44

@nvuillam
Copy link
Contributor Author

@abitrolly I'm already drowning with MegaLinter maintenance :)

But if MegaLinter users report issues or improvement ideas about CheckMake, i'll make sure to redirect them here :)

@abitrolly
Copy link

And why would other users do it? The only way I see is securing funding to retain maintainers. So while https://www.ox.security/?ref=megalinter raises funding, it could as well include things like https://backyourstack.com/ in their expense sheets.

@nvuillam
Copy link
Contributor Author

Ox Security is a startup and is already founding..... MegaLinter (so me !) , so open-source support is already in their expenses :D ( MegaLinter was an independent project before ^^ )

@abitrolly
Copy link

Right. This is what I am saying. Your investors want to be sure that your dependencies will not fall apart once you are out in the market.

@mrtazz
Copy link
Collaborator

mrtazz commented Nov 15, 2022

thanks for the contribution!

@mrtazz mrtazz merged commit 99dff53 into checkmake:main Nov 15, 2022
@nvuillam nvuillam deleted the patch-1 branch November 15, 2022 11:55
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