Skip to content

Conversation

mamueluth
Copy link
Member

Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:

  1. Limited scope. Your PR should do one thing or one set of things. Avoid adding “random fixes” to PRs. Put those on separate PRs.
  2. Give your PR a descriptive title. Add a short summary, if required.
  3. Make sure the pipeline is green.
  4. Don’t be afraid to request reviews from maintainers.
  5. New code = new tests. If you are adding new functionality, always make sure to add some tests exercising the code and serving as live documentation of your original intention.

To send us a pull request, please:

  • Fork the repository.
  • Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
  • Ensure local tests pass. (colcon test and pre-commit run (requires you to install pre-commit by pip3 install pre-commit)
  • Commit to your fork using clear commit messages.
  • Send a pull request, answering any default questions in the pull request interface.
  • Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

mamueluth and others added 30 commits July 29, 2024 11:26
* components check for export of interfaces
* change intefaces to allow custom export and test
* Fix rst syntax and some typos

* Fix rst syntax and small typos

* Fix clang issue
 * ddd basic test for error codes setting
 * docs for error and warning signals
 * add parsing of handle type for initialization of variant and adjust most tests
 * rename unclear variables
 * add changes for chainable controllers (epxport of rerference interfaces)
* add function for checking if handle holds value
Copy link

mergify bot commented Aug 26, 2024

This pull request is in conflict. Could you fix it @mamueluth?

Copy link

This PR is stale because it has been open for 45 days with no activity. Please tag a maintainer for help on completing this PR, or close it if you think it has become obsolete.

@github-actions github-actions bot added the stale label Apr 11, 2025
Copy link

mergify bot commented Apr 11, 2025

This pull request is in conflict. Could you fix it @mamueluth?

@github-actions github-actions bot removed the stale label Apr 14, 2025
Copy link

This PR is stale because it has been open for 45 days with no activity. Please tag a maintainer for help on completing this PR, or close it if you think it has become obsolete.

@github-actions github-actions bot added the stale label May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants