Skip to content

feature_request(behavior): create → write content → post #5

@Kristinita

Description

@Kristinita

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

  1. Extra blank recording in issues history.

2.2. Repositories maintainers

  1. Blank issues distract them.
  2. Maintainers can quickly close blank issue and do not pay attention to issue additions.
  3. 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: CreateCustom → I pasted Kristinita/kiragitlabdebugging (my GitLab repository for debugging) → I printed issue title Kira Example issue via StGitlabEnter.

3.3. Current behavior

Issue posted.

3.4. Expected behavior

As for GIssues Sublime Text package: create → write content → post.

GIssues

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions