Skip to content

Conversation

ShreyasManjunath
Copy link

…e building

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.

sachinkum0009 and others added 30 commits December 21, 2024 18:57
- minor code clean
- removed the template from license
- added one variable per line
- documented the enums
- updated the doc folder as per `joint_trajectory_controller`
Co-authored-by: Dr. Denis <[email protected]>
Co-authored-by: Dr. Denis <[email protected]>
- renamed service_buffer_ to gripper_service_buffer_
Co-authored-by: Dr. Denis <[email protected]>
Copy link

mergify bot commented Jun 17, 2025

@ShreyasManjunath, all pull requests must be targeted towards the master development branch.
Once merged into master, it is possible to backport to only-gpio-tool-controller, but it must be in master
to have these changes reflected into new distributions.

Copy link

github-actions bot commented Aug 4, 2025

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 Aug 4, 2025
@destogl destogl force-pushed the only-gpio-tool-controller branch from 57fdbcb to a3c9553 Compare August 16, 2025 19:24
@github-actions github-actions bot removed the stale label Aug 18, 2025
Copy link

mergify bot commented Aug 18, 2025

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

Copy link

github-actions bot commented Oct 3, 2025

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 Oct 3, 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.

3 participants