You are browsing as a guest. Sign up (or log in) to start making projects!

9h 47m 13s logged

Diagnostics done, other stuff too and some changes!

Diagnostics are now fully done! When something messes up, it will give you options to fix it!

Some time ago I created GitHub Synchronization settings for managing what to sync with GitHub, so what to retrieve and send with those options:

  • Sync status with GitHub repository
  • Sync badges with GitHub repository
  • Fetch GitHub repository topics
  • Fetch GitHub repository stats
  • Use GitHub’s language detection instead of Helyx’s

I created a brand new tab called ‘GitHub Actions’ where this setting is. GitHub Actions is meant to contain all of the actions that are mainly linked with GitHub endpoints.

I kept few such as Push, Pull, Sync in Git Actions due to how the layout is already created.

Also I added when you are rebasing and it fails, it automatically gives you a prompt to cancel it. So repair it…

GitHub Actions will contain a new stuff that will come to Helyx! Managing Issues and Pull Requests!! Maybe also workspaces/actions but I will see how difficult that is and how it is needed/useful in Helyx.

Another new function is, that when there’s an update for Helyx and I change the GitHub OAuth scope because of new features… Helyx will warn you and tell you to reauthorize to make sure every function will work correctly.

Before this change, Helyx was using its folder name as a name of the project and as a repository name for GitHub. Now, when you add a project to Helyx, Helyx will ask you what’s its name and when you will try to use some GitHub function for the first time on your newly added project on Helyx, it will request a GitHub Repository name from you. ;)

There’s still a lot of things to add. Honestly I thought that Helyx was at the very end like 50 hours ago and look! There are many more functions to add haha!

0
16

Comments 0

No comments yet. Be the first!