Allow developing composite actions within its own repository

[SimonSchwendele]

Description

I'm currently developing a lot of composite actions which should be used across a variety of repositories. This plugin however is currently only activated whenever the yml file resides in .github/workflows/*.yml

Background

You can push a composite action into its own repository and reference it like this

      - name: Do stuff with composite action
        uses: Owner/repo@branch
        with:
           input1: 'thing'
           input2: 'otherThing'

which means Im pushing repositories like this:

$ ls -a
.  ..  action.yml  .git   .gitignore  .idea
$ tree
.
└── action.yml

1 directory, 1 file

Request

This Plugin should recognize the existence of a compsite action

[YunaBraska]

Nice to know. I will have a look on this.

[YunaBraska]

Just to be sure that I understand this right...

Usecases

1) Local GitHub actions:

• .github/workflows/*.yml this is a local action which is loaded from the current local project
• There are ways to improve the recognition, e.g. https://github.com/YunaBraska/github-workflow-plugin/issues/16 2) uses: Owner/repo@branch that's a normal action loaded from the remote source. This should work already, as there is no difference if it's on the marketplace or not. You need to add your GitHub Account/Token to access private repos.

How are these two use cases connected? Or do you have a multimodule project?

[SimonSchwendele]

Okay there exists a private repository that contains the composite action

When I use that action in my actual workflows I can use the Intellisense quite well.'

However!

The request here is that I can't use the plugin during development. When I clone the repository in the first picture the plugin does not activate for action.yml because it's not somewhere at .github/workflows/

I currently have to rely on a link to trick the plugin

[YunaBraska]

Haha! The link is next level. Cool 👍 Understand, so I need to support actions which are not under the .github folder. Roger that.

[YunaBraska]

The new Version 2.2.7 (will be public in few days) will have a better support for local actions. Syntax Highlighting and also Code Completion for action.yml files is on my list. Therefore, not every Intellisense will work inside the action.yml files.

[YunaBraska]

2.2.7 is published. You should have basic support for action.yml files. Further development to support action.yml is postponed in #20 on the Project Board I hope you understand, I need to focus and bring the plugin in a stable position first. There are some clean-ups left. I will link this issue in #20, so your input is not lost! Please continue reporting me bugs, features and more. It's always good to know where I can improve this plugin.

[SimonSchwendele]

Thanks a lot. It looks great and ( nearly ) everything I use can be used by now.

One thing which is still missing ( not urgent tho ): When I assing a id theres no autocompletion for the stepnames:

[YunaBraska]

Yes, that's cause of the dirty fix I made. Background: I currently apply logic from GitHub Workflows to GitHub Actions. But some rules are different in GitHub Actions - like your example, where you can go over the steps directly without having jobs. That's not possible in workflows. I need to implement rules specific for GitHub Actions ^^ Therefore the task #20

[YunaBraska]

@SimonSchwendele i have rewritten the whole plugin to stabilize things. Do you have anything left of your wishlist? 😇

[SimonSchwendele]

@SimonSchwendele i have rewritten the whole plugin to stabilize things. Do you have anything left of your wishlist? 😇

Finally some holiday for me :) I'm gonna test something next week tho. Saw you released a new version, really appreciating all your hard effort :)