| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs: format releases.md | 1 年前 | |
chore: bump deps (#15151) | 2 个月前 | |
docs: refresh contributing & building guides, surface CLA signing flow (#15503) | 18 天前 | |
chore: move docs to folder | 3 年前 | |
docs: refresh contributing & building guides, surface CLA signing flow (#15503) | 18 天前 | |
chore: correct the wrong file path in building doc (#14145) When I read the [building-desktop-client-app.md](https://github.com/toeverything/AFFiNE/blob/canary/docs/building-desktop-client-app.md) to build Artifacts locally, I find there have some legacy path due to some project structure updates. So this is a litte fix to correct the unmatched path in the doc. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated desktop client app building documentation to reflect changes in the project structure and configuration setup. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai --> | 8 个月前 | |
feat(server): impl native reader for server (#14100) | 8 个月前 | |
docs: issue triaging document (#5071) I would like to sort out our process for handling github issues. When we receive a issue, we should first triage it. This PR contains the document about issue triaging. reference: [YouTrack issue states used in .NET tools team and their description](https://rider-support.jetbrains.com/hc/en-us/articles/360021572199-YouTrack-issue-states-used-in-NET-tools-team-and-their-description) [vscode Issues Triaging](https://github.com/microsoft/vscode/wiki/Issues-Triaging) | 2 年前 | |
docs: cleanup outdated infos | 6 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 2 个月前 | ||
| 18 天前 | ||
| 3 年前 | ||
| 18 天前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 2 年前 | ||
| 6 个月前 |