Skip to content

Workflow pentru pull requests #6

Open
Open
Workflow pentru pull requests#6

Description

@ionelmc
ionelmc
opened on May 9, 2015

Am putea avea un workflow de genul:

  • Cineva face fork, adauga un eveniment/pagina si dupa aceea face un PR
  • TravisCI ruleaza Pelican si publica HTMLul undeva (pentru review)
  • Daca e ok si se face merge la PR, TravisCI ruleaza din nou buildul, dar de data asta (fiindca nu e PR) face si deploy

Vis-a-vis de deploy, in TravisCI se pot stoca "secrete": http://docs.travis-ci.com/user/environment-variables/#Secure-Variables

Activity

  1. ionelmc
    changed the title [-]Workflow PRs[/-] [+]Workflow pull requests[/+] on May 9, 2015
  2. ionelmc
    changed the title [-]Workflow pull requests[/-] [+]Workflow pentru pull requests[/+] on May 9, 2015

  3. rciorba commented on May 10, 2015

    @rciorba
    rciorba
    on May 10, 2015

    Sună ok workflow-ul propus. Numai că apare întrebarea: cine poate să facă merge?

  4. PCManticore commented on May 10, 2015

    @PCManticore
    PCManticore
    on May 10, 2015
    Member

    Cine are drept de merge, ergo cineva din RoPython. Altfel nu văd de ce ar veni o terță persoană pentru a-și adăuga un eveniment ce ține de cu totul altceva.

  5. ionelmc commented on May 10, 2015

    @ionelmc
    ionelmc
    on May 10, 2015
    MemberAuthor

    Eu ma gandeam la PR ca si un workflow de drafting la anunt (cand sunt mai multi organizatori la un eveniment). E complet optional adica.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions