[Submit add-on]: TimerForNVDA-1.7.0.nvda-addon

[marlon-sousa]

Download URL

https://github.com/marlon-sousa/TimerForNVDA/releases/download/1.7.0/TimerForNVDA-1.7.0.nvda-addon

Source URL

https://github.com/marlon-sousa/TimerForNVDA

Publisher

Marlon Sousa

Channel

stable

License Name

Mit License

License URL

https://github.com/marlon-sousa/TimerForNVDA/blob/main/LICENSE

[seanbudd]

Please make sure to use the issue form to submit add-ons, not any AI tools, as per the submission guide

[marlon-sousa]

@seanbudd Hy Sean,

What is going on here?

First, I have read the submission guide and searched for IA and I haven't found anything.

Second, I am a long time nvda addon contributor and have had up until now a cordial relation-ship with you guys. TimerForNvda addon is well known by the community.

Third: what on earth does this submission have to do with IA?

I have a well established tagging system on my addons. We generate releases on tagging, and each time a tagging occurs I publish a new issue here. This has always been that way, and continues to be so. I cannot remember any complains ever on this addon.

The only thing I did now, to make my own life easier, was this: I coded (I'll repeat again: I coded) a github action to be executed after the release is published on my repo to open the issue automatically.

You probably didn't bother to check it out, so I will past it here to let things clear:

• name: Submit to NVDA Add-on Store
  id: submit-datastore
  if: github.repository == 'marlon-sousa/TimerForNVDA'
  env:
  GH_TOKEN: ${{ secrets.ADDON_DATASTORE_TOKEN }}
  TAG_NAME: ${{ github.ref_name }}
  REPO_URL: https://github.com/${{ github.repository }}
  run: |
  if [ -z "$GH_TOKEN" ]; then
  echo "ADDON_DATASTORE_TOKEN is not configured; skipping submission."
  {
  echo "## NVDA Add-on Store Submission"
  echo "- Skipped: ADDON_DATASTORE_TOKEN is not configured"
  } >> "$GITHUB_STEP_SUMMARY"
  exit 0
  fi

              ADDON_FILE=$(ls -1 *.nvda-addon | head -n 1)
              if [ -z "$ADDON_FILE" ]; then
                echo "No .nvda-addon file found."
                exit 1
              fi
  
              DOWNLOAD_URL="${REPO_URL}/releases/download/${TAG_NAME}/${ADDON_FILE}"
  
              # Channel in add-on store submission form is stable/beta/dev.
              # TimerForNVDA uses stable releases for tagged builds.
              CHANNEL="stable"
  
              ISSUE_TITLE="[Submit add-on]: ${ADDON_FILE}"
              ISSUE_BODY=$(printf '### Download URL\n%s\n\n### Source URL\n%s\n\n### Publisher\n%s\n\n### Channel\n%s\n\n### License Name\n%s\n\n### License URL\n%s\n' \
                "$DOWNLOAD_URL" \
                "$REPO_URL" \
                "Marlon Sousa" \
                "$CHANNEL" \
                "Mit License" \
                "https://github.com/marlon-sousa/TimerForNVDA/blob/main/LICENSE")
  
              ISSUE_URL=$(gh issue create \
                --repo nvaccess/addon-datastore \
                --title "$ISSUE_TITLE" \
                --label autoSubmissionFromIssue \
                --body "$ISSUE_BODY")
  
              echo "Created datastore issue: ${ISSUE_URL}"
              echo "addon_datastore_issue_url=${ISSUE_URL}" >> "$GITHUB_OUTPUT"
  
              {
                echo "## NVDA Add-on Store Submission"
                echo "- Datastore issue: ${ISSUE_URL}"
                echo "- Release tag: ${TAG_NAME}"
                echo "- Workflow run: ${REPO_URL}/actions/runs/${GITHUB_RUN_ID}"
              } >> "$GITHUB_STEP_SUMMARY"
  

The issue is opened on my name, with a token only I can generate on my gh account authorized for my repositories.

Now, would you tell me please what does this have to do with IA?

Thanks,
Marlom

[seanbudd]

You need to submit the add-on via the form. Typically AI tools use the CLI like you did to submit. This doesn't work. We need you to use the form, not the CLI or AI, to submit your add-ons.