Skip to content

ci: run CI on development branch pushes and PRs - #122

Closed
berlikm wants to merge 1 commit into
OpensourceICTSolutions:developmentfrom
berlikm:fix/ci-branch-filter
Closed

berlikm wants to merge 1 commit into
OpensourceICTSolutions:developmentfrom
berlikm:fix/ci-branch-filter

Conversation

@berlikm

@berlikm berlikm commented Jul 14, 2026 •

Copy link
Copy Markdown

Summary

CI never runs on this repo's working branch. 1.0.5 still triggers on develop and pull_request only for main, so PRs into development get no check run.

Rebased onto 1.0.5 development (36fb2c4).

  • ci.yml: push trigger development (was develop); add development to pull_request branches
  • Keep 1.0.5's NetBox v4.6.7 pin (this PR does not retarget CI at main)
  • DEVELOPMENT.md: replace stale develop references

Two files, no functional plugin change. Merge first so every subsequent PR gets a real signal.

Scope frozen at tip b6f77d8.

Rebased onto 1.0.5. Keep the NetBox v4.6.7 pin; switch the push/PR
triggers from the obsolete develop branch to development.

Co-authored-by: berlikm <[email protected]>
@cursor
cursor Bot force-pushed the fix/ci-branch-filter branch from 78bf537 to b6f77d8 Compare August 14, 2026 11:49
@berlikm

berlikm commented Aug 14, 2026

Copy link
Copy Markdown
Author

Rebased this onto current 1.0.5 development (36fb2c4).

1.0.5 still triggered CI on develop / main only, so PRs into development never got a check run. This branch now:

  • pushes/PRs against development (and main)
  • keeps the 1.0.5 NetBox v4.6.7 pin (I did not retarget CI at netbox main)
  • updates DEVELOPMENT.md so it matches the real working branch

Independent of the feature stack. Please merge this first so the rest of the PRs get a real CI signal.

@berlikm berlikm closed this Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants