admin/openhuman
1
0
Fork 0
mirror of https://github.com/tinyhumansai/openhuman.git synced 2026-07-27 21:08:00 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
6d6be24e5969fdb134bbb2c26551ec4059bc8a0c
openhuman/.github/pull_request_template.md
T
Steven EnamakelandGitHub 5d6c9e7333 refactor: replace OpenClaw AI config flow and standardize PR template (#21) 
* refactor: update AI configuration handling and remove OpenClaw integration

- Replaced OpenClaw context injection with direct AI configuration retrieval methods.
- Introduced new functions for fetching and refreshing AI configuration, enhancing modularity.
- Cleaned up the AIPanel component to utilize the new configuration structure.
- Removed obsolete OpenClaw-related files and logic to streamline the codebase.
- Added new TODO items for future enhancements in the documentation.

* docs: add PR template and update AI authoring rules

- Introduced a new pull request template in `.github/pull_request_template.md` to standardize PR submissions.
- Updated CLAUDE.md to require the use of the new PR template for all pull requests.
- Added a rule in AGENTS.md specifying that agents must adhere to the PR template when suggesting content.

* chore: update subproject commit and refine pre-push script

- Updated the subproject commit reference in the skills directory.
- Refined the pre-push script to improve formatting and linting checks, ensuring automatic fixes are applied when issues are detected.

* refactor: improve label formatting in AIPanel component

- Adjusted label formatting in the AIPanel component for better readability by breaking long lines into multiple lines.
- Ensured consistent styling for labels related to personality, safety rules, tools, and skills overview.
2026-03-26 19:35:23 -07:00

817 B
Raw Blame History

Summary

  • What changed and why.
  • Keep this to 3-6 bullets focused on user-visible or architecture-impacting changes.

Problem

  • What issue or risk this PR addresses.
  • Include context needed for reviewers to evaluate correctness quickly.

Solution

  • How the implementation solves the problem.
  • Note important design decisions and tradeoffs.

Testing

  • yarn -s compile
  • cargo check --manifest-path src-tauri/Cargo.toml
  • Other checks run (list commands)
  • Manual validation completed (list scenarios)

Impact

  • Runtime/platform impact (desktop/mobile/web/CLI), if any.
  • Performance, security, migration, or compatibility implications.

Breaking Changes

  • None
  • Yes (describe clearly, including migration steps)

Related

  • Issue(s):
  • Follow-up PR(s)/TODOs:
Reference in New Issue View Git Blame Copy Permalink