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 00:40:55 UTC
[incubator-devlake-website] branch main updated (084216cf -> e21d18dd)
This is an automated email from the ASF dual-hosted git repository.
abeizn pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
from 084216cf [Docs] improve Overview/Introduction.md
new b1240bed fix: fixed broken image links in teams doc
new 23cd92d1 fix: fixed typo
new e21d18dd Revert "fix: fixed broken image links in teams doc"
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/UserManuals/TeamConfiguration.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[incubator-devlake-website] 01/03: fix: fixed broken image links in teams doc
Posted by ab...@apache.org.
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 b1240bed0c14d68b3a6fcf7db59385599f5394dc
Author: Keon Amini <ke...@gmail.com>
AuthorDate: Wed Jul 13 19:53:41 2022 -0500
fix: fixed broken image links in teams doc
---
docs/UserManuals/TeamConfiguration.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/UserManuals/TeamConfiguration.md b/docs/UserManuals/TeamConfiguration.md
index 4646ffa8..6ef12925 100644
--- a/docs/UserManuals/TeamConfiguration.md
+++ b/docs/UserManuals/TeamConfiguration.md
@@ -31,7 +31,7 @@ b. The actual api request.
iii. After successful execution, the teams table is generated and the data can be seen in the database table teams.
(Notes: how to connect to the database: mainly through host, port, username, password, and then through sql tools, such as sequal ace, datagrip and other data, of course you can also access through the command line mysql -h `ip` -u `username` -p -P `port`)
-
+
## Step 2 - Construct user tables (roster)
@@ -52,11 +52,11 @@ b. The actual api request.
iii. After successful execution, the users table is generated and the data can be seen in the database table users.
-
+
iv. Generated the team_users table, you can see the data in the team_users table.
-
+
## Step 3 - Update users if you need
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)
@@ -64,7 +64,7 @@ If there is a problem with team_users association or data in users, just re-put
## Step 4 - Collect accounts
accounts table is collected by users through devlake. You can see the accounts table information in the database.
-
+
## Step 5 - Automatically match existing accounts and users through api requests
@@ -91,7 +91,7 @@ curl --location --request POST '127.0.0.1:8080/pipelines' \
b. After successful execution, the user_accounts table is generated, and you can see the data in table user_accounts.
-
+
## Step 6 - Get user_accountsr relationship
After generating the user_accounts relationship, the user can get the associated data through the GET method to confirm whether the data user and account match correctly and whether the matched accounts are complete.
@@ -103,7 +103,7 @@ b. The corresponding curl command:
curl --location --request GET 'http://127.0.0.1:8080/plugins/org/user_account_mapping.csv'
```
-
+
c. You can also use sql statements to determine, here to provide a sql statement for reference only.
```
@@ -123,7 +123,7 @@ curl --location --request PUT 'http://127.0.0.1:8080/plugins/org/user_account_ma
b. You can see that the data in the user_accounts table has been updated.
-
+
**The above is the flow of user usage for the whole team feature.**
[incubator-devlake-website] 02/03: fix: fixed typo
Posted by ab...@apache.org.
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 23cd92d1caf9430f572ff4ad7e97f69e38386dff
Author: Keon Amini <ke...@gmail.com>
AuthorDate: Wed Jul 13 21:59:16 2022 -0500
fix: fixed typo
---
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 6ef12925..16d1d26d 100644
--- a/docs/UserManuals/TeamConfiguration.md
+++ b/docs/UserManuals/TeamConfiguration.md
@@ -93,7 +93,7 @@ b. After successful execution, the user_accounts table is generated, and you can
-## Step 6 - Get user_accountsr relationship
+## Step 6 - Get user_accounts relationship
After generating the user_accounts relationship, the user can get the associated data through the GET method to confirm whether the data user and account match correctly and whether the matched accounts are complete.
a. http://127.0.0.1:8080/plugins/org/user_account_mapping.csv (put into the browser to download the file directly)
[incubator-devlake-website] 03/03: Revert "fix: fixed broken image links in teams doc"
Posted by ab...@apache.org.
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 e21d18dd6b6fe5e5699f2eed0f59b14ef395f8df
Author: Keon Amini <ke...@gmail.com>
AuthorDate: Thu Jul 14 11:12:59 2022 -0500
Revert "fix: fixed broken image links in teams doc"
This reverts commit 7a6af8911737989069e4c000f2e9d51f702852e1.
---
docs/UserManuals/TeamConfiguration.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/UserManuals/TeamConfiguration.md b/docs/UserManuals/TeamConfiguration.md
index 16d1d26d..0834b969 100644
--- a/docs/UserManuals/TeamConfiguration.md
+++ b/docs/UserManuals/TeamConfiguration.md
@@ -31,7 +31,7 @@ b. The actual api request.
iii. After successful execution, the teams table is generated and the data can be seen in the database table teams.
(Notes: how to connect to the database: mainly through host, port, username, password, and then through sql tools, such as sequal ace, datagrip and other data, of course you can also access through the command line mysql -h `ip` -u `username` -p -P `port`)
-
+
## Step 2 - Construct user tables (roster)
@@ -52,11 +52,11 @@ b. The actual api request.
iii. After successful execution, the users table is generated and the data can be seen in the database table users.
-
+
iv. Generated the team_users table, you can see the data in the team_users table.
-
+
## Step 3 - Update users if you need
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)
@@ -64,7 +64,7 @@ If there is a problem with team_users association or data in users, just re-put
## Step 4 - Collect accounts
accounts table is collected by users through devlake. You can see the accounts table information in the database.
-
+
## Step 5 - Automatically match existing accounts and users through api requests
@@ -91,7 +91,7 @@ curl --location --request POST '127.0.0.1:8080/pipelines' \
b. After successful execution, the user_accounts table is generated, and you can see the data in table user_accounts.
-
+
## Step 6 - Get user_accounts relationship
After generating the user_accounts relationship, the user can get the associated data through the GET method to confirm whether the data user and account match correctly and whether the matched accounts are complete.
@@ -103,7 +103,7 @@ b. The corresponding curl command:
curl --location --request GET 'http://127.0.0.1:8080/plugins/org/user_account_mapping.csv'
```
-
+
c. You can also use sql statements to determine, here to provide a sql statement for reference only.
```
@@ -123,7 +123,7 @@ curl --location --request PUT 'http://127.0.0.1:8080/plugins/org/user_account_ma
b. You can see that the data in the user_accounts table has been updated.
-
+
**The above is the flow of user usage for the whole team feature.**