-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show how to view changes to the SVN files in VS Code #86
Comments
It seems that VS Code forgets about the SVN repo if you close and restart the workspace. However you can get the source control pane to recognise it again by running an SVN command that connects to the remotes repository, e.g.
to bring in the latest updates, or
if we just want to see what has changed since we checked out the repository. As this is a little involved, it is probably best to make a separate help page on viewing changes. |
I had another look at this and found a setting which seems to fix the issue of SVN repos not appearing in the Source Control pane when you restart:
Can you add this to the |
Adding to devcontainer.json file did the work
|
#88 fixes the issue of SVN repos being forgotten about when the codespace is restarted. So now we can go back to the original issue in #86 (comment), i.e. add an example of viewing the changes to askYesNo.R in the contributor workflow example. |
I think we can just add this inside "Updating source code page" |
If we turn off the connection to git repo (#85) it is much easier to track changes to the SVN repo (or repos) that people have checked out.
It would be good to include a screen shot of this as part of one of the demos.
It would be something like
But probably based on on the askYesNo example, so that we can include it after this step in the Contribution Workflow: https://contributor.r-project.org/r-dev-env/tutorials/contribution_workflow/#2-editing-source-code or perhaps as another mini help page "Viewing changes" with a note on how to open the accessible diff viewer (three dots menu/F7).
The text was updated successfully, but these errors were encountered: