Update scmsync documentation #332
Conversation
xml/obs_scm_bridge.xml
Outdated
| have to happen inside of the SCM provider instance. OBS will just verify the authenticity of that resource in | ||
| future.</para> | ||
| <para>This allows to run the entire packaging source update in an external SCM repository using the | ||
| native tooling. It is recommended to have this SCM server on the same trust level as the OBS |
There was a problem hiding this comment.
The first sentence of this paragraph is potentially unclear in two ways.
First, it refers to "the entire packaging source update" - the definite article ("the") indicates that there is some definite (specific) packaging source update that is being referred to, but I'm not sure this is the case? What do you mean by "the entire packaging source update", here, exactly?
Second, it says "using the native tooling". Again, the definite article is used, but I'm not sure the reader knows which "native tooling" you mean here?
There was a problem hiding this comment.
tried to be more clear now.
xml/obs_scm_bridge.xml
Outdated
| different or not all. For example you can not use automatic package source merging via _link files anymore. | ||
| This means also that workflows inside of OBS are not working anymore or are limited. A submit or release | ||
| request would still work with a scmsync source, but the user would manually need to specify the target always. | ||
| Functionality for project managed resources is even more limited.</para> |
There was a problem hiding this comment.
Can you give an example or two of these "project managed resources" for readers who aren't familiar with this term?
There was a problem hiding this comment.
I have reworeded this now.
xml/obs_scm_bridge.xml
Outdated
| @@ -127,7 +147,7 @@ | |||
| by referencing it via the scmsync meta tag. | |||
| </para> | |||
| <para> | |||
| This has been only implemented for gitea atm, you can find details in the <link xlink:href="https://github.com/adrianschroeter/obs-gitea-bridge">obs-gitea-bridge</link> documentation. | |||
| This has been only implemented for gitea atm, you can find details in the <link xlink:href="https://github.com/openSUSE/obs-gitea-bridge">obs-gitea-bridge</link> documentation. | |||
There was a problem hiding this comment.
The SCM bridge has so far only been implemented for gitea. You can find details in . . .
There was a problem hiding this comment.
not the scmsync, but the update notification. changed that now.
changed defaults and changed recommendations
adrianschroeter
force-pushed
the
scmsync
branch
from
b8f449e
to
c8ce571
Compare
smithfarm
force-pushed
the
scmsync
branch
2 times, most recently
from
4079c63
to
3575250
Compare
Signed-off-by: Nathan Cutler <ncutler@suse.com>
changed defaults and changed recommendations