Update README.md

[noahtalerman]

• Remove the "why"
  • @noahtalerman: Hypothesis is that users who land here want to get started fast. They already know the why or don't care
• Remove note about fleetctl gitops. Users don't interact w/ it
• Simplify headers

[noahtalerman]

Remove the "why"

FYI @rachaelshaw I took this TODO

[noahtalerman]

Hey @getvictor unrelated to this PR, what do we use this Fleet GitOps repo in GitLab for? https://gitlab.com/developers6254743/fleet-gitops

I was recently invited.

[getvictor]

Hey @getvictor unrelated to this PR, what do we use this Fleet GitOps repo in GitLab for? https://gitlab.com/developers6254743/fleet-gitops

I was recently invited.

We need a GitLab repo to test the GitLab CI (.gitlab-ci.yml). It is a mirror of this repo. But we need the URL to be something like https://gitlab.com/fleetdm/fleet-gitops
I'm waiting for @lukeheath to sort it out.

[noahtalerman]

We need a GitLab repo to test the GitLab CI (.gitlab-ci.yml).

@getvictor ah, ok.

Will our users ever interact w/ it? Or is the best practice to clone the GitHub repo using GitLab?

Wondering b/c, as someone new to GitLab, I'm confused looking at the steps in the README:

How do I clone the repo if I'm using GitLab? Do I create a GitLab repo after I clone the GitHUb repo?

[getvictor]

We need a GitLab repo to test the GitLab CI (.gitlab-ci.yml).

@getvictor ah, ok.

Will our users ever interact w/ it? Or is the best practice to clone the GitHub repo using GitLab?

Wondering b/c, as someone new to GitLab, I'm confused looking at the steps in the README:

How do I clone the repo if I'm using GitLab? Do I create a GitLab repo after I clone the GitHUb repo?

Both GitHub and GitLab use git. So terms like clone and push are git-specific, and don't refer to any specific git UI. If the repo is mirrored in both GitHub and GitLab, then users can clone from either place.

[lukeheath]

@noahtalerman @getvictor I created it: https://gitlab.com/fleetdm/fleet-gitops

@getvictor You should have access but let me know if not.

[noahtalerman]

If the repo is mirrored in both GitHub and GitLab, then users can clone from either place.

@getvictor does this mean that any change (commit) in GitHub will be reflected in GitLab and vice versa?

@getvictor, the changes in this PR are my pass at simplifying the setup instructions. What do you think?

For later:

Now that we have a GitHub and GitLab repo, my understanding is that we could simplify the setup steps further by removing these steps:

I think we can come back to this later. My understanding is that this would require making changes to the GitHub and GitLab repos and maintaining these repos separately.

[getvictor]

@noahtalerman Commit to GitHub will be reflected in GitLab, but not vice versa.

The changes look good.

The deletion step 4 is optional, so we could simply remove it.

[getvictor]

Looks good. One comment.

[getvictor]

At this point, the pipeline/action will run and fail because the secrets are not present. We could call it out.

[noahtalerman]

he pipeline/action will run and fail because the secrets are not present.

@getvictor only for GitLab right? I added a note.

[getvictor]

For both (although I haven't tried this updated flow with GitLab)

[noahtalerman]

For both

Added for both.

Ah, ok. If it's quick, do you mind giving the updated instructions a go? Don't want to promote a best practice that we haven't tried ourselves.

Let me know if trying them isn't quick. I can pull the updated instructions out into a separate story that we can address later.

[noahtalerman]

The deletion step 4 is optional, so we could simply remove it.

Removed it 👍

[noahtalerman]

Decided to merge this.

If we learn that the new instructions don't work we can quickly update.