Results 1 to 7 of 7

Thread: Source Control

  1. #1

    Default Answered: Source Control

    My project working directory has nearly 7000 files. It is based on the Master/Detail Basic project.

    What files/directories must I commit to my source control repository for another developer to work on this project?

    Thanks.

  2. Quote Originally Posted by Phil.Strong View Post
    I would ignore:
    build, ext, bootstrap.json, .sencha

    e.g. .gitignore file
    Code:
    .sencha
    build
    ext
    bootstrap.json
    we should update the docs to represent this.
    Awesome, thanks!

    Can/should I also exclude .architect? It seems that when I check out the project and open it in Architect, I can't save it due to a conflict with the existing .architect.

    What about /packages? There are a lot of theme related files in packages too and while I had tried more than one them I only see one listed as a resource in architect.

    Thanks again,
    Barry

  3. #2
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,488
    Answers
    74
    Aaron Conran
    @aconran

  4. #3

    Default

    I read through the docs before asking. This states that I need to check-in the entire project. Do I really need the contents of build, ext, packages etc? Isn't it pretty much apps, metadata and resources?

  5. #4
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Answers
    15

    Default

    I would ignore:
    build, ext, bootstrap.json, .sencha

    e.g. .gitignore file
    Code:
    .sencha
    build
    ext
    bootstrap.json
    we should update the docs to represent this.
    Phil Strong
    @philstrong

  6. #5

    Default

    Quote Originally Posted by Phil.Strong View Post
    I would ignore:
    build, ext, bootstrap.json, .sencha

    e.g. .gitignore file
    Code:
    .sencha
    build
    ext
    bootstrap.json
    we should update the docs to represent this.
    Awesome, thanks!

    Can/should I also exclude .architect? It seems that when I check out the project and open it in Architect, I can't save it due to a conflict with the existing .architect.

    What about /packages? There are a lot of theme related files in packages too and while I had tried more than one them I only see one listed as a resource in architect.

    Thanks again,
    Barry
    Last edited by greenbba; 21 Mar 2014 at 10:05 AM. Reason: Adding question of .architect

  7. #6
    Sencha User Phil.Strong's Avatar
    Join Date
    Mar 2007
    Location
    Olney, MD
    Posts
    1,953
    Answers
    15

    Default

    packages are things you install into your project that you would want checked in.

    .architect is a nice addition to this list. Yeah go ahead and add that as well.
    Phil Strong
    @philstrong

  8. #7
    Sencha Premium User
    Join Date
    Jul 2016
    Posts
    2

    Default

    Regarding the documentation at: http://docs.sencha.com/architect/3/g...team_apps.html

    Can the "Check the Project Into Source" section be updated to reflect the advice given here in this thread?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •