jx import should be able to handle repos which the user does not have write access

[jstrachan]

so rather than doing git commit; git push it generates a new branch (maybe in a fork) and generates a Pull Request with any changes

[i0n]

We were talking about this today! Perhaps I'll have a look.

[jstrachan]

yeah! I wonder if we could query if we had write access; or maybe a CLI argument could decide if import does a PR or a commit/push? I guess the downside of doing a PR to change, say, a Jenkinsfile is if there's an old one in there already its gonna fail. Though I guess a more common use case is there's no Dockerfile/Jenkinsfile so we could still register the project in Jenkins then when the PR is merged, it'd enable the real pipeline?

I guess forking the repo before updating is another option too. Maybe we start with a CLI flag for fork v PR?

[rawlingsj]

/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.