Re: Request for GitLab account approval
ronnie sahlberg <[email protected]> Thu, 2 Oct 2025 20:22:57 +1000
| Newsgroups | gmane.comp.video.videolan.vlc.devel |
|---|---|
| Message-ID | <CAN05THTEBXvfaCAtCpYyna0rpdf=KCQo0q8RuQyQ_d8_vtQg6g@mail.gmail.com> |
On Thu, 2 Oct 2025 at 20:11, Mohit Shukla <[email protected]> wrote: > > Hello VLC developers, > > I’ve just subscribed to this mailing list and created an account on code.videolan.org > (mail: [email protected]). I’d like to contribute to VLC by starting with [bug fixing / > documentation / testing / small features]. > > Could you please approve my GitLab account? Maybe I am misunderstanding something, but why do you need your account approved? Generally, when you contribute to a GitLab/GitHub/...something else... project you never have permissions to contribute directly. Instead the common workflow is that you 1, fork the project into a private fork on GitLab and this is what you checkout git clone locally. Then when you want to do a change: 2, create a new branch locally to work on the new change you want to do. 3, create the change locally, with nice commit messages and the testing you need, then "git push" the new branch to YOUR fork of the gitlab project. 4, then on GitLab, in your fork/branch you create a pull request to the upstream, i.e. core VLC Repository. When it is reviewed and if it is accepted, they will then import/merge the changes from YOUR repository into the upstream repo. But it is not like SVN or other/older version control systems. You never contribute by committing your changes directly into upstream. > > Thanks, > Mohit Shukla, > IIT Bhubaneswar. > _______________________________________________ > vlc-devel mailing list > To unsubscribe or modify your subscription options: > https://mailman.videolan.org/listinfo/vlc-devel _______________________________________________ vlc-devel mailing list To unsubscribe or modify your subscription options: https://mailman.videolan.org/listinfo/vlc-devel