It would be nice, if would be possible post issues after creating. Don't post blank issues.
2. Argumentation
I'm not sure, that current creating issues behavior is better.
2.1. History
Extra blank recording in issues history.
2.2. Repositories maintainers
Blank issues distract them.
Maintainers can quickly close blank issue and do not pay attention to issue additions.
They can solve, that StGitlab user is spammer, and block it.
3. Example
3.1. Reproducibility
I reproduce the problem in the newest version of stable portable Sublime Text without plugins and user settings.
3.2. Steps to reproduce
Ctrl+Shift+P (⌘⇧p for Mac) → Gitlab issue: Create → Custom → I pasted Kristinita/kiragitlabdebugging (my GitLab repository for debugging) → I printed issue title Kira Example issue via StGitlab → Enter.
It would be nice to have the same behavior (create → write content → post) for snippets. Currently, StGitlab post blank snippets (example) as blank issues.
1. Summary
It would be nice, if would be possible post issues after creating. Don't post blank issues.
2. Argumentation
I'm not sure, that current creating issues behavior is better.
2.1. History
2.2. Repositories maintainers
3. Example
3.1. Reproducibility
I reproduce the problem in the newest version of stable portable Sublime Text without plugins and user settings.
3.2. Steps to reproduce
Ctrl+Shift+P (⌘⇧p for Mac) →
Gitlab issue: Create
→Custom
→ I pastedKristinita/kiragitlabdebugging
(my GitLab repository for debugging) → I printed issue titleKira Example issue via StGitlab
→ Enter.3.3. Current behavior
Issue posted.
3.4. Expected behavior
As for GIssues Sublime Text package: create → write content → post.
4. Snippets
It would be nice to have the same behavior (create → write content → post) for snippets. Currently, StGitlab post blank snippets (example) as blank issues.
Thanks.