You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TODO.md
+3-18
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,7 @@
1
1
# MVP
2
2
What needs to be done before the tool can actually be used.
3
-
-[X] Implement all required gitlab API
4
-
- APIs
5
-
- Add members
6
-
- Delete members
7
-
- Update members
8
-
- On adding handle error User Already Exists
9
-
- On removing handle error User Not Found
10
-
- Add corresponding output to error handling (Already Added, Not Found)
11
-
12
-
-[ ] Get rid of billions of loops and start using HashMaps
13
3
-[ ] Add tests
14
-
-[X] Create a Dockerfile and GitHub Actions for tests and releases
15
-
-[ ] Refactor whole arguments module. Maybe rewrite it to methods or something
16
4
-[ ] Refactor error handling
17
-
-[ ] Write good documentation in README.md
18
5
19
6
# Nice to have
20
7
-[ ] Add a `describe` command foreach config entity
@@ -32,8 +19,6 @@ What needs to be done before the tool can actually be used.
32
19
```
33
20
34
21
-[ ] Async actions
35
-
-[ ] Get rid of state file
36
-
-[X] Use spinners for output
37
22
-[ ] Add auto suggestions for every command
38
23
-[ ] Start versioning the config file and add possibility to migrate from to a newer version. And add kinda annotation to let gum know it's a gum-config. Something like that
39
24
```
@@ -63,8 +48,8 @@ What needs to be done before the tool can actually be used.
63
48
```
64
49
And remove each user, which is being updated anyhow, from groups provided via head_groups (remove from groups, sub groups and projects)
65
50
66
-
-[] Remove extra fields from state. State should only contain IDs and access_level
67
-
-[] Auto check for updates
51
+
-[X] Remove extra fields from state. State should only contain IDs and access_level
52
+
-[X] Auto check for updates
68
53
-[ ] Add feature for inviting users, if it's possible.
69
54
When user is invited, he won't have an id until he confirms invitation. But after he confirms, he will be added to projects where he's been invited. So I think it should look like that:
70
55
- New object is added to config
@@ -75,7 +60,7 @@ And remove each user, which is being updated anyhow, from groups provided via he
75
60
teams: []
76
61
groups: []
77
62
```
78
-
- On each sync this invites should be checked for confirmation (if there so no such possibility, the whole invite ting seems impossible)
63
+
- On each sync this invites should be checked for confirmation (if there so no such possibility, the whole invite thing seems impossible)h
79
64
- If it's confirmed, the user should be automatically added to users and to state
80
65
-[ ] Add patterns for checking users emails and usernames
0 commit comments