WSDG: Consistent capitalization for GitLab
Use consistent and proper capitalization for GitLab throughout the WSDG.
This commit is contained in:
parent
4bbc640763
commit
14880b13ba
|
@ -415,7 +415,7 @@ someone answers your question.
|
||||||
|
|
||||||
[#ChIntroBugDatabase]
|
[#ChIntroBugDatabase]
|
||||||
|
|
||||||
==== Bug Database (Gitlab Issues)
|
==== Bug Database (GitLab Issues)
|
||||||
|
|
||||||
The Wireshark community collects bug reports in an issues database at {wireshark-bugs-url}.
|
The Wireshark community collects bug reports in an issues database at {wireshark-bugs-url}.
|
||||||
This database is filled with manually filed bug reports, usually after some discussion on wireshark-dev, and automatic bug reports from continuous integration jobs.
|
This database is filled with manually filed bug reports, usually after some discussion on wireshark-dev, and automatic bug reports from continuous integration jobs.
|
||||||
|
@ -470,7 +470,7 @@ can help you.
|
||||||
If you send captured data to the mailing lists, or add it to your bug report,
|
If you send captured data to the mailing lists, or add it to your bug report,
|
||||||
be sure it doesn't contain any sensitive or confidential information,
|
be sure it doesn't contain any sensitive or confidential information,
|
||||||
such as passwords. Visibility of such files can be limited to certain
|
such as passwords. Visibility of such files can be limited to certain
|
||||||
groups in the Gitlab Issues database by marking the issue confidential.
|
groups in the GitLab Issues database by marking the issue confidential.
|
||||||
====
|
====
|
||||||
|
|
||||||
==== Reporting Crashes on UNIX-like platforms
|
==== Reporting Crashes on UNIX-like platforms
|
||||||
|
|
|
@ -637,12 +637,12 @@ See {wireshark-wiki-url}FuzzTesting for details.
|
||||||
|
|
||||||
When you're satisfied with your changes (and obtained any necessary
|
When you're satisfied with your changes (and obtained any necessary
|
||||||
approval from your organization) you can upload them for review at
|
approval from your organization) you can upload them for review at
|
||||||
{wireshark-code-review-url}. This requires a Gitlab account
|
{wireshark-code-review-url}. This requires a GitLab account
|
||||||
as described at <<ChSrcGitRepository>>.
|
as described at <<ChSrcGitRepository>>.
|
||||||
|
|
||||||
You need to fork your repository which will became yours, and you will have write access to it. Once
|
You need to fork your repository which will became yours, and you will have write access to it. Once
|
||||||
you are done with your changes, push them to a branch of your choice (as snowcone-machine). Now in the
|
you are done with your changes, push them to a branch of your choice (as snowcone-machine). Now in the
|
||||||
Gitlab's UI a message will tell you that you created a new branch and a button to create a merge request.
|
GitLab's UI a message will tell you that you created a new branch and a button to create a merge request.
|
||||||
|
|
||||||
|
|
||||||
[source,sh]
|
[source,sh]
|
||||||
|
|
|
@ -488,7 +488,7 @@ In many cases you can use a tool like link:https://www.tracewrangler.com/[TraceW
|
||||||
====
|
====
|
||||||
Do not send large files (> 1 MB) to the mailing lists. Instead, provide a
|
Do not send large files (> 1 MB) to the mailing lists. Instead, provide a
|
||||||
download link. For bugs and feature requests, you can create an issue on
|
download link. For bugs and feature requests, you can create an issue on
|
||||||
link:{wireshark-bugs-url}[Gitlab Issues] and upload the file there.
|
link:{wireshark-bugs-url}[GitLab Issues] and upload the file there.
|
||||||
====
|
====
|
||||||
|
|
||||||
==== Reporting Crashes on UNIX/Linux platforms
|
==== Reporting Crashes on UNIX/Linux platforms
|
||||||
|
|
Loading…
Reference in New Issue