Knott+Win10 wrote:
mbasagli wrote:
You can try this:
https://gitlab.com/-/ide/project/mattba ... /master/-/it shows an editor where you can add and edit files. then it should prompt you to create a merge request
ok.. if that is step 1. i get this.. ( see image )
at this point what is step 2?
OK. step 2. is click on "FORK" . TY Mattbas. I can create a group or subgroup. i think in respect it should be a subgroup with a path back to knotter? does that sound ok? if i were to give it a name it would be Knotter _Plugins_ Working_Code , ie plugins that work at least on version 9.6, using the standard three file addition. ? so... i reach step 3 Matt, and welcome your thoughts before creating it. The reason i think it should be a subgroup, is that though the code works for me in Win 10, i cant vouch for any other user.. such is the addition of first time code. ? so.. i think it should be a " child " attached to knotter, viewable by public users of knotter with gitlab access - just like i have, and the methods you have given so far.. which- as creator, are your own.. ive just cleverly reused info on knotter which was already visible to anyone with .js ability, using win 10 ui, and the variables and Visual Studio Code = i can access. so its a child of knotter... Matt if you want a specific path and names, now is the time before i try to create step 3. if we can manage this, then i can create a text of steps.. for those who want to add code,(that works) and a text of steps for those who want to use it. ? i.e i can give users star code version 1, others might use that and create star code version 2 etc etc.. i want to protect users from spam and code that does not do what knotter can use, ( it needs control )this mo, i am here.
https://docs.gitlab.com/ee/user/group/s ... index.html