GitHub and Visualisation

[Joseph Gilvary]

Welcome to Java Ranch @Brent Laster

I am interested in learning how GitHub will drive develpment to IDE virtualization.  I have played with GitLab but am hoping it evolves into a viable development platform for my work

[Brent Laster]

Hi Joseph, sorry but I'm not clear on the question.  Please feel free to add more information.  The title mentions Visualization - GitHub is primarily a browser-based interface similar to GitLab (since you mentioned you've played with that). Actions has a browser-based interface built into GitHub through the "Actions" tab in the repository view that shows past runs, a job graph with color-coding for success/failure etc. - similar to the type of information presented in the Stage View of Jenkins if you're familiar with that.

You also mentioned IDE virtualization. Did you mean visualization? GitHub integrates well with multiple IDEs - especially ones like VS Code.  There is also GitHub Codespaces which provide a virtual dev environment - that's worth checking out if you're interested in virtual dev environments.  For most repositories you can find it under a tab when you select the "Code" version.

[Roland Mueller]

Joseph Gilvary wrote:Welcome to Java Ranch @Brent Laster

I am interested in learning how GitHub will drive develpment to IDE virtualization.  I have played with GitLab but am hoping it evolves into a viable development platform for my work

I think the basic idea of github actions is not to provide yet another full IDE rather than a dedicated feature that can be integrated into existing systems - whether they are IDEs or simple editors.

Then the CI/CD approach is to automate builds and let them trigger e.g. by git repository events. In contrast an IDE provides interactive working on code. Both approaches are valid and definitely do not exclude each other.