You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by ab...@apache.org on 2022/07/15 02:02:39 UTC
[incubator-devlake-website] 04/06: fix: team configuration collect accounts
This is an automated email from the ASF dual-hosted git repository.
abeizn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
commit 06c3c7748868e2ea963aec00ac4e52f817d7a48c
Author: abeizn <zi...@merico.dev>
AuthorDate: Thu Jul 14 18:42:11 2022 +0800
fix: team configuration collect accounts
---
docs/UserManuals/TeamConfiguration.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/UserManuals/TeamConfiguration.md b/docs/UserManuals/TeamConfiguration.md
index 0834b969..76453f7c 100644
--- a/docs/UserManuals/TeamConfiguration.md
+++ b/docs/UserManuals/TeamConfiguration.md
@@ -62,7 +62,7 @@ b. The actual api request.
If there is a problem with team_users association or data in users, just re-put users api interface, i.e. (b in step 2 above)
## Step 4 - Collect accounts
-accounts table is collected by users through devlake. You can see the accounts table information in the database.
+The accounts table is collected by users through devlake. In order to match with users and facilitate the demonstration of subsequent functions, here I construct fake accounts data from the information in the users table. For real user collection, you need to run the corresponding plugin service through devlake, for example, the github plugin, and after running the corresponding plugin service, the accounts data will be generated.
