Anonymous
1 year agoNot applicable
Status:
New
Git Ignore option for Source Control
Automate source control commits unless marked for Git Ignore. Easy method to identify trial or PoC work that should not be in version controlled.
2 Comments
- nielsvdc
Super User
I support the idea of being able to exclude items from being committed to Git. Especially since ML Model and Experiment items are now supported for Git. But you should also be able to ignore items by prefix or other identifier or maybe even workspace folder name. - liquorichrisRegular VisitorI support this idea as well. Can source control support the .gitigore file? If not, implement a .fabricignore file similar to .artifactignore in Azure DevOps?
Recent ideas
Dedicated Fabric Message Center to communicate planned Fabric Changes
Summary Microsoft recently rolled out a change that automatically enabled the Item Recovery tenant setting in Microsoft Fabric for tenants where the setting had not been explicitly configured. Accor...Edgar_8 hours agoNew MemberNew32Views5likes0CommentsWorkspace-Level Control of Storage Modes (Import vs DirectQuery vs Direct Lake)
Organizations operating under strict governance and data residency requirements need the ability to control which storage modes are permitted within a workspace. Currently, report authors can choose...masoodaftab9 hours agoNew MemberNew6Views0likes0CommentsGranular Workspace Permissions Beyond Workspace Roles
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } The current workspace access model is limited to the predefined workspac...masooddevcorp9 hours agoNew MemberNew19Views1like0CommentsAccessibility issue in the Share dialog of embedded Power BI reports
Accessibility issue in the Share dialog of embedded Power BI reports I would like to share an accessibility finding identified while testing an embedded Power BI report published as part of the cont...ugartema13 hours agoNew MemberNew10Views1like0Comments