Skip to content

Conversation

@jsoref
Copy link
Contributor

@jsoref jsoref commented Oct 12, 2025

Generic requirements in order to contribute to MISP:

  • One Pull Request per fix/feature/change/...
  • Keep the amount of commits per PR as small as possible: if for any reason, you need to fix your commit after the pull request, please squash the changes in one single commit (or tell us why not)
  • Always make sure it is mergeable in the default branch (as of today 2020-05-05: branch 2.4)
  • Please make sure Travis CI works on this request, or update the test cases if needed
  • Any major changes adding a functionality should be disabled by default in the config

What does it do?

Update code of conduct link for current release

Questions

  • Does it require a DB change? No
  • Are you using it in production? No
  • Does it require a change in the API (PyMISP for example)? No

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
@adulau
Copy link
Member

adulau commented Oct 13, 2025

Thank you! It makes sense.

@adulau adulau merged commit 4b2ebbd into MISP:2.5 Oct 13, 2025
2 checks passed
@jsoref jsoref deleted the update-issue-templates-branch-to-2.5 branch October 13, 2025 13:11
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.

2 participants