Add option that, instead of creating few separate issues, would make the action create single issue with list/checklist of rss updates.

I tested this action and found that it didn't output issues.

Looks like the output was commented out?

Hello!

I'm trying to use the action in the repository (thanks for sharing) although I'm receiving a SIGSEV that I'm not able to know the root cause of it (limited Go knowledge sorry).

My testing setup is for checking nvidia package updates on Ubuntu Focal is as follow:

Run guilhem/[email protected]
  with:
    repo-token: ***
    feed: https://packages.ubuntu.com/focal/updates/newpkg?format=rss
    prefix: [Ubuntu Focal Nvidia 2022-05-02]
    characterLimit: 255
    dry-run: false
    lastTime: 24h
    labels: ubuntu
    titleFilteR: .*nvidia-graphics-drivers-390.*
/usr/bin/docker run --name ghcrioguilhemrssissuesaction051_f0b8b7 --label 294b31 --workdir /github/workspace --rm -e INPUT_REPO-TOKEN -e INPUT_FEED -e INPUT_PREFIX -e INPUT_CHARACTERLIMIT -e INPUT_DRY-RUN -e INPUT_LASTTIME -e INPUT_LABELS -e INPUT_TITLEFILTER -e INPUT_AGGREGATE -e INPUT_CONTENTFILTER -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/security-advisories/security-advisories":"/github/workspace" ghcr.io/guilhem/rss-issues-action:0.5.1
New Ubuntu Packages
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7c36a7]

goroutine 1 [running]:
main.main.func1(0x1?)
	/src/main.go:102 +0x27
reflect.Value.call({0x7fb5a0?, 0xc000451c00?, 0xc0001859d8?}, {0x88320c, 0x4}, {0xc000185af0, 0x1, 0xc000185a08?})
	/usr/local/go/src/reflect/value.go:556 +0x845
reflect.Value.Call({0x7fb5a0?, 0xc000451c00?, 0x0?}, {0xc000185af0, 0x1, 0x1})
	/usr/local/go/src/reflect/value.go:339 +0xbf
github.com/thoas/go-funk.Filter({0x7eed40?, 0xc00048f9c8}, {0x7fb5a0?, 0xc000451c00})
	/go/pkg/mod/github.com/thoas/[email protected]/presence.go:41 +0x337
main.main()
	/src/main.go:101 +0x627

Am I doing some wrong with the configuration? Thanks!

If I don't include the labels field with this action, creating the issue fails with:

Warning: Fail create issue <ISSUE TITLE>: POST https://api.github.com/repos/<ORG>/<REPO>/issues: 422 Validation Failed [{Resource:Label Field:name Code:missing_field Message:}]

This seems to be due to always including the labels in the new issue request, even though it may be empty:

I was able to work around this by configuring the action to add a label with the labels field.

Hello!

As a member of the Kubernetes Upstream Marketing team, we would love to use this GitHub Action to create issues for us in our repo. But, there needs to be a license. Would you be willing to open source this project under MIT or Apache 2 Licenses?

Doc: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository

It would be interesting if you had the option of not bringing all the text of the article, but just a few characters and a 'Read more: www.xpto.com'
RSS is bringing all the content from all the sites, and that ends up taking away the article's view.

My sugestion:

Create characterLimit options.

• Default value: 0
  • If the person does not enter a value other than 0, they will continue to create an issue with all the content of the article, which is the current behavior.
• If the person reports a value above 0, actions will create the issue with the number of characters defined, 3 points at the end (...) and the footer Read more: XXX.

Workflow Example:

on:
  schedule:
    - cron: "0 11 * * *"

jobs:

  AssertQA:
    runs-on: ubuntu-latest
    steps:
      - uses: guilhem/[email protected]
        with:
          repo-token: ${{ secrets.GITHUB_TOKEN }}
          feed: "https://medium.com/feed/assertqualityassurance"
          lastTime: "25h"
          labels: "AssertQA,RSS"
          characterLimit: 250

Issue example:

Hello guys,
Continuing on reviewing some performance test tools, today is the turn of Jmeter and Gatling, which looks like more and more people are using nowadays. Remember always check your other options and see what better fits for your project...

Read more: https://azevedorafaela.com/2020/06/22/load-tests-jmeter-vs-gatlin/

But I had no good idea.

Any suggestion?

I noticed that this Action gobbled up my minutes rather quickly. So I gave it a try to convert it to Javascript, and it is a lot faster (less than 20 seconds, when the Docker-based version typically takes about one and a half minutes).

You can find the current state here: https://github.com/guilhem/rss-issues-action/compare/dscho:switch-to-javascript

I do understand that this conversion might cause more problems than it solves (because regular expression syntax differs between Go and Javascript), so I am prepared to hear the answer "No" to the question whether I should open a Pull Request.

At the same time, I also noticed that some input parameters are kebap-cased, others are camelCased (I plan on addressing this while at it).

Oh, and I also noticed that the current Go code has a bug: while it declares the aggregate input correctly, the actual code looks for aggragate, which of course does not exist (notice the a in the second syllable).

add assignees/notify field so that it is possible to ping a particular user(s)