Skip to content

Commit 9e9836b

Browse files
prettier
1 parent 421fe0b commit 9e9836b

File tree

7 files changed

+144
-140
lines changed

7 files changed

+144
-140
lines changed

CONTRIBUTING.md

+33-32
Original file line numberDiff line numberDiff line change
@@ -15,32 +15,34 @@ By contributing to Eliza, you agree that your contributions will be licensed und
1515

1616
We believe in the power of the OODA Loop - a decision-making framework that emphasizes speed and adaptability. OODA stands for:
1717

18-
- **Observe**: Gather information and insights about the project, the community, and the broader AI ecosystem.
19-
- **Orient**: Analyze your observations to identify opportunities for contribution and improvement.
20-
- **Decide**: Choose a course of action based on your analysis. This could be proposing a new feature, fixing a bug, or creating content.
21-
- **Act**: Execute your decision and share your work with the community.
18+
- **Observe**: Gather information and insights about the project, the community, and the broader AI ecosystem.
19+
- **Orient**: Analyze your observations to identify opportunities for contribution and improvement.
20+
- **Decide**: Choose a course of action based on your analysis. This could be proposing a new feature, fixing a bug, or creating content.
21+
- **Act**: Execute your decision and share your work with the community.
2222

2323
## How to Contribute
2424

2525
### For Developers
2626

2727
1. **Extend Eliza's Capabilities**
28-
- Develop new actions, evaluators, and providers
29-
- Improve existing components and modules
28+
29+
- Develop new actions, evaluators, and providers
30+
- Improve existing components and modules
3031

3132
2. **Enhance Infrastructure**
32-
- Review open issues and submit PRs
33-
- Test and update documentation
34-
- Optimize performance
35-
- Improve deployment solutions
3633

37-
1. Fork the repo and create your branch from `main`.
34+
- Review open issues and submit PRs
35+
- Test and update documentation
36+
- Optimize performance
37+
- Improve deployment solutions
38+
39+
3. Fork the repo and create your branch from `main`.
3840
1. The name of the branch should start with the issue number and be descriptive of the changes you are making.
3941
1. eg. 40--add-test-for-bug-123
40-
2. If you've added code that should be tested, add tests.
41-
3. Ensure the test suite passes.
42-
4. Make sure your code lints.
43-
5. Issue that pull request!
42+
4. If you've added code that should be tested, add tests.
43+
5. Ensure the test suite passes.
44+
6. Make sure your code lints.
45+
7. Issue that pull request!
4446

4547
## Styleguides
4648

@@ -74,18 +76,17 @@ This section lists the labels we use to help us track and manage issues and pull
7476
- `documentation` - Issues or pull requests related to documentation.
7577
- `good first issue` - Good for newcomers.
7678

77-
7879
## Getting Help
7980

80-
- Join [Discord](https://discord.gg/ai16z)
81-
- Check [FAQ](docs/community/faq.md)
82-
- Create GitHub issues
81+
- Join [Discord](https://discord.gg/ai16z)
82+
- Check [FAQ](docs/community/faq.md)
83+
- Create GitHub issues
8384

8485
## Additional Resources
8586

86-
- [Local Development Guide](docs/guides/local-development.md)
87-
- [Configuration Guide](docs/guides/configuration.md)
88-
- [API Documentation](docs/api)
87+
- [Local Development Guide](docs/guides/local-development.md)
88+
- [Configuration Guide](docs/guides/configuration.md)
89+
- [API Documentation](docs/api)
8990

9091
## Contributor Guide
9192

@@ -101,19 +102,19 @@ In the interest of fostering an open and welcoming environment, we as contributo
101102

102103
Examples of behavior that contributes to creating a positive environment include:
103104

104-
- Using welcoming and inclusive language
105-
- Being respectful of differing viewpoints and experiences
106-
- Gracefully accepting constructive criticism
107-
- Focusing on what is best for the community
108-
- Showing empathy towards other community members
105+
- Using welcoming and inclusive language
106+
- Being respectful of differing viewpoints and experiences
107+
- Gracefully accepting constructive criticism
108+
- Focusing on what is best for the community
109+
- Showing empathy towards other community members
109110

110111
Examples of unacceptable behavior include:
111112

112-
- The use of sexualized language or imagery and unwelcome sexual attention or advances
113-
- Trolling, insulting/derogatory comments, and personal or political attacks
114-
- Public or private harassment
115-
- Publishing others' private information without explicit permission
116-
- Other conduct which could reasonably be considered inappropriate in a professional setting
113+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
114+
- Trolling, insulting/derogatory comments, and personal or political attacks
115+
- Public or private harassment
116+
- Publishing others' private information without explicit permission
117+
- Other conduct which could reasonably be considered inappropriate in a professional setting
117118

118119
#### Our Responsibilities
119120

docs/README.md

+3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,9 @@
11
# Eliza - Multi-agent simulation framework
2+
23
# https://github.com/ai16z/eliza
4+
35
# Visit https://eliza.builders for support
6+
47
# dev branch
58

69
<img src="./docs/static/img/eliza_banner.jpg" alt="Eliza Banner" width="100%" />

docs/docs/community/best-practices.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -44,4 +44,4 @@ It is imperative to run all existing tests (`pnpm test`) before creating a PR to
4444

4545
## Branching Strategy
4646

47-
All new features and bug fixes must target the `main` branch, except when they are specific to a previously released version. In such scenarios, the bug fix PR should target the respective release branch. If necessary, changes will be backported from the `main` branch to a release branch, excluding any modifications that involve consensus-breaking features or API changes.
47+
All new features and bug fixes must target the `main` branch, except when they are specific to a previously released version. In such scenarios, the bug fix PR should target the respective release branch. If necessary, changes will be backported from the `main` branch to a release branch, excluding any modifications that involve consensus-breaking features or API changes.

docs/docs/community/contributing.md

+17-4
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
First off, thank you for considering contributing to Eliza! We welcome contributions from everyone, regardless of experience level. 🎉
44

55
## Table of Contents
6+
67
- [Contribution License Agreement](#contribution-license-agreement)
78
- [Code of Conduct](#code-of-conduct)
89
- [OODA Loop Framework](#the-ooda-loop-a-framework-for-contribution)
@@ -30,13 +31,15 @@ We pledge to make participation in our project a harassment-free experience for
3031
### Our Standards
3132

3233
Positive behavior includes:
34+
3335
- Using welcoming and inclusive language
3436
- Being respectful of differing viewpoints
3537
- Gracefully accepting constructive criticism
3638
- Focusing on what is best for the community
3739
- Showing empathy towards others
3840

3941
Unacceptable behavior includes:
42+
4043
- Harassment of any kind
4144
- Discriminatory jokes and language
4245
- Publishing others' private information
@@ -56,18 +59,19 @@ We follow the OODA Loop for decision-making:
5659
### For Developers
5760

5861
1. **Development Process**
62+
5963
```bash
6064
# Fork and clone
6165
git clone https://github.com/yourusername/eliza.git
6266
cd eliza
63-
67+
6468
# Create branch (include issue number)
6569
git checkout -b 123-add-new-feature
66-
70+
6771
# Make changes, test, and commit
6872
npm test
6973
git commit -m "feat: add new feature"
70-
74+
7175
# Push and create PR
7276
git push origin 123-add-new-feature
7377
```
@@ -82,43 +86,52 @@ We follow the OODA Loop for decision-making:
8286
## Pull Request Guidelines
8387

8488
### PR Title Format
89+
8590
```
8691
feat|fix|docs|style|refactor|test|chore: title
8792
```
8893

8994
### PR Template
95+
9096
```markdown
9197
# Relates to:
98+
9299
[Link to issue]
93100

94101
# Background
102+
95103
- What does this PR do?
96104
- What kind of change is this?
97105

98106
# Testing
107+
99108
- How to test the changes
100109
- Screenshots (if UI changes)
101110

102111
# Documentation
112+
103113
- Required documentation changes
104114
```
105115

106116
## Styleguides
107117

108118
### Git Commit Messages
119+
109120
- Use present tense ("Add feature" not "Added feature")
110121
- Use imperative mood ("Move cursor" not "Moves cursor")
111122
- Limit first line to 72 characters
112123
- Reference issues after first line
113124

114125
### Code Style
126+
115127
- JavaScript: Follow [JavaScript Standard Style](https://standardjs.com/)
116128
- TypeScript: Follow [TypeScript Standard Style](https://github.com/standard/ts-standard)
117129
- Documentation: Use [Markdown](https://daringfireball.net/projects/markdown/)
118130

119131
## Recognition and Rewards
120132

121133
Contributors can earn:
134+
122135
- "Github - Contributors" role on Discord
123136
- Direct communication with a16z devs
124137
- Recognition for outstanding contributions
@@ -132,4 +145,4 @@ Contributors can earn:
132145

133146
---
134147

135-
Thank you for contributing to Eliza and helping build the future of autonomous AI agents! 🚀
148+
Thank you for contributing to Eliza and helping build the future of autonomous AI agents! 🚀

packages/core/src/tests/videoGeneration.test.ts

+32-28
Original file line numberDiff line numberDiff line change
@@ -26,36 +26,40 @@ const mockVideoGenerationPlugin = {
2626
const apiKey = runtime.getSetting("LUMA_API_KEY");
2727
return !!apiKey;
2828
}),
29-
handler: vi.fn().mockImplementation(async (runtime, message, state, options, callback) => {
30-
// Initial response
31-
callback({
32-
text: "I'll generate a video based on your prompt",
33-
});
34-
35-
// Check if there's an API error
36-
const fetchResponse = await global.fetch();
37-
if (!fetchResponse.ok) {
38-
callback({
39-
text: "Video generation failed: API Error",
40-
error: true,
41-
});
42-
return;
43-
}
44-
45-
// Final response with video
46-
callback(
47-
{
48-
text: "Here's your generated video!",
49-
attachments: [
29+
handler: vi
30+
.fn()
31+
.mockImplementation(
32+
async (runtime, message, state, options, callback) => {
33+
// Initial response
34+
callback({
35+
text: "I'll generate a video based on your prompt",
36+
});
37+
38+
// Check if there's an API error
39+
const fetchResponse = await global.fetch();
40+
if (!fetchResponse.ok) {
41+
callback({
42+
text: "Video generation failed: API Error",
43+
error: true,
44+
});
45+
return;
46+
}
47+
48+
// Final response with video
49+
callback(
5050
{
51-
source: "videoGeneration",
52-
url: "https://example.com/video.mp4",
51+
text: "Here's your generated video!",
52+
attachments: [
53+
{
54+
source: "videoGeneration",
55+
url: "https://example.com/video.mp4",
56+
},
57+
],
5358
},
54-
],
55-
},
56-
["generated_video_123.mp4"]
57-
);
58-
}),
59+
["generated_video_123.mp4"]
60+
);
61+
}
62+
),
5963
},
6064
],
6165
};

packages/create-eliza-app/README.md

-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,6 @@ deno run -A npm:create-eliza-app@latest path
3232

3333
<!-- /automd -->
3434

35-
3635
## Command Line Arguments
3736

3837
- `--name`: Name of the template to use (default: "eliza")

0 commit comments

Comments
 (0)