Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1800

Closed
Open
Created Oct 25, 2012 by Administrator@rootOwner

Gitlab web editor feature does not work as expected.

Created by: severity1

The usual clone push pull stuff works, anything I commit is updated to gitlab's user page, however using the web editor, after editing a file, adding a comment and clicking on commit I see a message saying "Your changes have been successfully committed", but upon checking the file my changes was not committed at all.

The commit itself does not even update to the user page, and when I git pull the same repo from my local no changes are made. It seems as if gitlab is saying the web editor made a successful commit but it actually never made a commit to the underlying gitolite system.

Recent changes to the gitlab server in question is that:

  1. gitolite was updated from v2 -> v3
  2. gitlab was updated from v2.9.1 -> v3.0.1

After the changes I ran the usual sanity checks: root@gitserver-beta:/opt/gitlab/gitlab# sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production Starting diagnostics config/database.yml............exists config/gitlab.yml............exists /opt/git/repositories/............exists /opt/git/repositories/ is writable?............YES remote: Counting objects: 800, done. remote: Compressing objects: 100% (645/645), done. remote: Total 800 (delta 243), reused 0 (delta 0) Receiving objects: 100% (800/800), 73.64 KiB, done. Resolving deltas: 100% (243/243), done. Can clone gitolite-admin?............YES UMASK for .gitolite.rc is 0007? ............YES /opt/git/.gitolite/hooks/common/post-receive exists? ............YES Validating projects repositories: test-repo1.....post-receive file ok test-repo2.....post-receive file ok test-repo3.....post-receive file ok calvin-project.....post-receive file ok puppet-modules.....post-receive file ok hiera-inhouse.....post-receive file ok scripts.....post-receive file ok

Finished

Assignee
Assign to
Time tracking