Scheduled service maintenance on November 22


On Friday, November 22, 2024, between 06:00 CET and 18:00 CET, GIN services will undergo planned maintenance. Extended service interruptions should be expected. We will try to keep downtimes to a minimum, but recommend that users avoid critical tasks, large data uploads, or DOI requests during this time.

We apologize for any inconvenience.

#18 issue utilities

開啟中
sprenger5 年之前創建 · 5 條評論

I noticed two things which are not working as expected when creating issues / PRs.

  • Checkboxes can not be ticked directly, but need to be change in the source
  • people can not be mentioned via '@person', or at least there is no mechanism for listing suggested people to mention
I noticed two things which are not working as expected when creating issues / PRs. - [ ] Checkboxes can not be ticked directly, but need to be change in the source - people can not be mentioned via '@person', or at least there is no mechanism for listing suggested people to mention
Michael Sonntag 評論 4 年之前'
所有者

The mention feature was added upstream and should be available by now.

The mention feature was added upstream and should be available by now.
sprenger 評論 3 年之前'
發佈者

Thanks! I tested the mentions feature and a correct link is inserted when stating @author. However there is no list of suggestions popping up when starting to write @a. So I guess users might frequently not notice the feature as they don't receive immediate feedback when typing. Is this a matter of configuration of the webinterface or is this extended functionality also not present upstream?

Thanks! I tested the mentions feature and a correct link is inserted when stating `@author`. However there is no list of suggestions popping up when starting to write `@a`. So I guess users might frequently not notice the feature as they don't receive immediate feedback when typing. Is this a matter of configuration of the webinterface or is this extended functionality also not present upstream?

Not a feature upstream and my javascript isn't strong enough to tackle that tbh. Should we keep the issue open for that or close it and open another one?

Not a feature upstream and my javascript isn't strong enough to tackle that tbh. Should we keep the issue open for that or close it and open another one?
sprenger 評論 3 年之前'
發佈者

As you want. Maybe forwarding this to an upstream issue would be the best option here.

As you want. Maybe forwarding this to an upstream issue would be the best option here.
https://github.com/gogs/gogs/issues/2957
登入 才能加入這對話。
未選擇里程碑
未指派成員
3 參與者
正在加載...
取消
保存
尚未有任何內容