Skip to content

Conversation

@quabynah-bilson
Copy link
Member

Description

What -

Why -

How -

Type of change

Please leave one option from the following and delete the rest:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • New Integration (non-breaking change which adds a new integration)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Non-breaking change (fix of existing functionality that will not change current behavior)
  • Documentation (added/updated documentation)

All tests should be run against the port production environment(using a testing org).

Core testing checklist

  • Integration able to create all default resources from scratch
  • Resync finishes successfully
  • Resync able to create entities
  • Resync able to update entities
  • Resync able to detect and delete entities
  • Scheduled resync able to abort existing resync and start a new one
  • Tested with at least 2 integrations from scratch
  • Tested with Kafka and Polling event listeners
  • Tested deletion of entities that don't pass the selector

Integration testing checklist

  • Integration able to create all default resources from scratch
  • Completed a full resync from a freshly installed integration and it completed successfully
  • Resync able to create entities
  • Resync able to update entities
  • Resync able to detect and delete entities
  • Resync finishes successfully
  • If new resource kind is added or updated in the integration, add example raw data, mapping and expected result to the examples folder in the integration directory.
  • If resource kind is updated, run the integration with the example data and check if the expected result is achieved
  • If new resource kind is added or updated, validate that live-events for that resource are working as expected
  • Docs PR link here

Preflight checklist

  • Handled rate limiting
  • Handled pagination
  • Implemented the code in async
  • Support Multi account

Screenshots

Include screenshots from your environment showing how the resources of the integration will look.

API Documentation

Provide links to the API documentation used for this integration.

dennis-bilson and others added 18 commits October 29, 2025 23:11
Signed-off-by: Dennis Bilson <dennis@teksol.com.gh>
Signed-off-by: Dennis Bilson <dennis.bilson@port.io>
Signed-off-by: Dennis Bilson <dennis@teksol.com.gh>
- Added dedicated GraphQL query LIST_ORG_MEMBER_WITH_BOTS_GQL for fetching org members including bots
- Simplified user filtering by using specific query based on include_bots flag instead of post-filtering
- Added alias "includeBots" for the include_bots field in GithubUserSelector
- Improved email filtering logic to properly handle bot accounts
- Removed redundant type checking since bot filtering is now handled at query level

Signed-off-by: Dennis Bilson <dennis.bilson@port.io>
- Rewrote sanitize_login function to better handle consecutive brackets and edge cases
- Split bracket replacement into distinct steps for clearer logic:
  1. Replace consecutive ][ with single dash
  2. Replace remaining [ with dash
  3. Replace ] with dash except when at end of string
- Uncommented and updated test cases to verify correct handling of various login formats
- Removed edge cases from test suite that were no longer neede
- Eliminated unnecessary `include_bots` condition when filtering users without email.
- Updated test case to include an email field for validation.
…ings

- Updated gsub patterns for creator, assignees, and reviewers to fix inconsistencies in bracket sanitization.
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.

5 participants